[GH-ISSUE #1272] Bitwarden iOS app doesn't work after changing urls. #890

New issue

Closed

opened 2026-03-03 02:04:25 +03:00 by kerem · 2 comments

kerem commented

2026-03-03 02:04:25 +03:00

Owner

Originally created by @tkreindler on GitHub (Dec 20, 2020).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1272

Subject of the issue

My server was working perfectly with my old domain name (.ddns.net) through noip, but when I switched to a new domain name (.mooo.com) through afraid.org I began having issues exclusively through the iOS app. All other clients and connections work perfectly. Encryption is done through lets encrypt, I've tried deleting and reinstalling the client, completely resetting my Bitwarden installation, all to no avail. For whatever reason no matter what I try with my new url I get the error: "An error has occurred. Exception message: The operation couldn't be completed. Invalid argument." on account login or creation on the iOS app only. The server logs show no sign of a connection attempt made. It certainly seems like some sort of TLS error but the certs work perfectly on all my other clients, plus I have multiple other services on this server using the same TLS certs with no problems.

Your environment

Bitwarden_rs version: 1.17.0

Install method: Docker image
Clients used: iOS, Safari, Web, MacOS
Reverse proxy and version:
Version of mysql/postgresql:
Other relevant information:

Steps to reproduce

Create a Bitwarden_rs server guarded with letsencrypt hosted on *.mooo.com using afraid.org free DDNS.

Expected behaviour

Actual behaviour

"An error has occurred. Exception message: The operation couldn't be completed. Invalid argument."

Relevant logs

None unfortunately, the app makes no connection to the server.

Originally created by @tkreindler on GitHub (Dec 20, 2020). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1272  ### Subject of the issue  My server was working perfectly with my old domain name (*.ddns.net) through noip, but when I switched to a new domain name (*.mooo.com) through afraid.org I began having issues exclusively through the iOS app. All other clients and connections work perfectly. Encryption is done through lets encrypt, I've tried deleting and reinstalling the client, completely resetting my Bitwarden installation, all to no avail. For whatever reason no matter what I try with my new url I get the error: "An error has occurred. Exception message: The operation couldn't be completed. Invalid argument." on account login or creation on the iOS app only. The server logs show no sign of a connection attempt made. It certainly seems like some sort of TLS error but the certs work perfectly on all my other clients, plus I have multiple other services on this server using the same TLS certs with no problems. ### Your environment   * Bitwarden_rs version: 1.17.0  * Install method: Docker image * Clients used: iOS, Safari, Web, MacOS * Reverse proxy and version:  * Version of mysql/postgresql:  * Other relevant information: ### Steps to reproduce  Create a Bitwarden_rs server guarded with letsencrypt hosted on *.mooo.com using afraid.org free DDNS. ### Expected behaviour  Login and account creation successful. ### Actual behaviour  "An error has occurred. Exception message: The operation couldn't be completed. Invalid argument." ### Relevant logs  None unfortunately, the app makes no connection to the server.

kerem closed this issue

2026-03-03 02:04:25 +03:00

kerem commented

2026-03-03 02:04:26 +03:00

Author

Owner

@tkreindler commented on GitHub (Dec 20, 2020):

Supplement: This issue only pops up on certain iOS devices, might have to move this upstream if it ends up being something with the app. Trying to narrow down to see if there's a more specific issue.

@tkreindler commented on GitHub (Dec 20, 2020): Supplement: This issue only pops up on certain iOS devices, might have to move this upstream if it ends up being something with the app. Trying to narrow down to see if there's a more specific issue.

kerem commented

2026-03-03 02:04:26 +03:00

Author

Owner

@tkreindler commented on GitHub (Dec 20, 2020):

Adguard dns was the issue.

@tkreindler commented on GitHub (Dec 20, 2020): Adguard dns was the issue.