mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-07-17 01:12:27 -05:00
Bitwarden iOS app doesn't work after changing urls. #885
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @tkreindler on GitHub (Dec 20, 2020).
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
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.
@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):
Adguard dns was the issue.