Still cannot login to selfhost server from iOS app

I can login to my selfhosted instance from webpage, with no problem. Having issues logging in via latest iOS app.
My selfhosted host is hosted on a custom port. Port 442.

I can get to it via safari web browser, and login as expected. But if I try to login via iOS app, it just says “an error occurred.” no other message. Just :“an error occurred.”

My self hosted address is a publicly available dns name: https://myCloudfront.domainName.com:442
(renamed here, because I don’t want my host to suddenly get unwanted pings : )…but the protocol and ports here are the same as what is use. )

I put this url into the iOS app, under the “server URL” in the ‘self host’ section.

I put in my user name and then right when I go to the iOS app section where I put in my password it immediately says: “an error occured”. even before I put in my password. I still try my password, and then hit 'login with master password" button. it then shows the “an error occured” message again.

I have tried:
rebooting selfhosted server
uninstall iOS app, and reinstall iOS app.
rebooting phone.

None of this has solved my issue.

My phone is on iOS18. I was able to login, via the app, before I upgraded to iOS 18. I’m selfhosting Bitwarden, not vaultwarden. I’m selfhosting Bitwarden Version 2.21.1.

What am I missing? Why can I login via web browser, but not login to my selfhosted via the Bitwarden iOS app?

@muxketeer Hi!

???

There is no Bitwarden server version 2.21.1. (Releases · bitwarden/server · GitHub)

Hi @Nail1684 .
I just grabbed that version number from the webpage UI. Perhaps that is the version of something else.
See image grab from my web page ui.

Okay, that is an old version, possibly of the web app then?!

Please, can you do the following? Go to the Dashboard of your Admin Portal , which displays your server and web version. Make a screenshot and post it here.

I ran into issue getting to the admin web ui.
But I have the versions from my
/home/bitwarden/bitwarden.sh

# Please do not create pull requests modifying the version numbers.
COREVERSION="2022.9.1"
WEBVERSION="2022.9.1"
KEYCONNECTORVERSION="2022.5.0"

Are these the version numbers you need?

Well, yeah…

It seems you never updated anything, right? The good news, if you update the server version to the latest (I think 2024.9.1), you should be able to login with the iOS app again.

Some advice for the future: the updates bring security and feature updates. Your versions had their last updates relatively exactly 24 months ago. From a security standpoint, that is not recommended, to say it mildly. :wink:

Of course, waiting a few days with new updates is not a bad idea… but you should update regularly. BTW the web app / web vault as well. If you self-host, you have to take care of that, otherwise, I think, the cloud-option would be far more secure. (PS: also the machine / OS where you host Bitwarden, has to be up-to-date, to ensure security and all…)

One possibility, to remember oneself could be to at least subscribe to the Bitwarden Release Notes (Release Notes | Bitwarden Help Center) per email, and to use that as a reminder…

Links to Bitwarden-GitHub:
Bitwarden server: Releases · bitwarden/server · GitHub
Bitwarden clients: Releases · bitwarden/clients · GitHub

Link to Bitwarden-Self-Host: GitHub - bitwarden/self-host: Bitwarden's self-hosted release repository

PS: Make a backup before updating! And here is some info about making updates and more to “self-hosting” in the Bitwarden Help Sites: Update your Instance | Bitwarden Help Center

I tried to do a

 ./bitwarden.sh update

and that appeared to pull new versions. with output that included

 _     _ _                         _
| |__ (_) |___      ____ _ _ __ __| | ___ _ __
| '_ \| | __\ \ /\ / / _` | '__/ _` |/ _ \ '_ \
| |_) | | |_ \ V  V / (_| | | | (_| |  __/ | | |
|_.__/|_|\__| \_/\_/ \__,_|_|  \__,_|\___|_| |_|


bitwarden.sh version 2024.9.1
Docker version 20.10.7, build f0df350
Docker Compose version v2.11.2

and the docker portion

[+] Running 14/14
 ⠿ Container bitwarden-attachments    Removed                                                   7.2s
 ⠿ Container bitwarden-notifications  Removed                                                  14.8s
 ⠿ Container bitwarden-events         Removed                                                  13.4s
 ⠿ Container bitwarden-sso            Removed                                                  18.9s
 ⠿ Container bitwarden-icons          Removed                                                  14.4s
 ⠿ Container bitwarden-nginx          Removed                                                  14.4s
 ⠿ Container bitwarden-portal         Removed                                                  18.4s
 ⠿ Container bitwarden-admin          Removed                                                  10.1s
 ⠿ Container bitwarden-api            Removed                                                   9.9s
 ⠿ Container bitwarden-identity       Removed                                                   8.1s
 ⠿ Container bitwarden-web            Removed                                                   8.5s
 ⠿ Container bitwarden-mssql          Removed                                                   3.5s
 ⠿ Network docker_public              Removed                                                   0.4s
 ⠿ Network docker_default             Removed                                                   0.6s
2024.9.1: Pulling from bitwarden/setup
a2318d6c47ec: Pull complete
6e2e0959c9eb: Pull complete
ca6981920ae5: Pull complete
4dc62e745685: Pull complete
f63d9359ee11: Pull complete
d89081998fcd: Pull complete
9aa04c95c825: Pull complete
971aa78d0744: Pull complete
e5c8bd3cb819: Pull complete
35e9b2810521: Pull complete
8d308898555f: Pull complete
Digest: sha256:dea9de66ef85d21997ec2b096ceea292a37e7d5fda4d73bf50dc9bd565e51308
Status: Downloaded newer image for bitwarden/setup:2024.9.1
docker.io/bitwarden/setup:2024.9.1
Failed to create CoreCLR, HRESULT: 0x80070008
:~$

that

docker.io/bitwarden/setup:2024.9.1
Failed to create CoreCLR, HRESULT: 0x80070008

seems unhappy.

however, if I do a $ ./bitwarden.sh start

it still starts it up…

Using default tag: latest
latest: Pulling from certbot/certbot
Digest: sha256:ddf9e5d226a56e886986838fa0ebedc0237511c78664352e8d0f4346ee022cd8
Status: Image is up to date for certbot/certbot:latest
docker.io/certbot/certbot:latest
Saving debug log to /etc/letsencrypt/logs/letsencrypt.log

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Processing /etc/letsencrypt/renewal/MYDOMAINHOSTHERE.conf
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Certificate not yet due for renewal

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
The following certificates are not due for renewal yet:
  /etc/letsencrypt/live/MYDOMAINHOSTHERE/fullchain.pem expires on 2024-11-13 (skipped)
No renewals were attempted.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[+] Running 14/14
 ⠿ Network docker_public              Created                                                   0.2s
 ⠿ Network docker_default             Created                                                   0.2s
 ⠿ Container bitwarden-identity       Started                                                  24.0s
 ⠿ Container bitwarden-notifications  Started                                                  17.3s
 ⠿ Container bitwarden-sso            Started                                                  21.1s
 ⠿ Container bitwarden-attachments    Started                                                   7.3s
 ⠿ Container bitwarden-events         Started                                                  18.0s
 ⠿ Container bitwarden-web            Started                                                  13.5s
 ⠿ Container bitwarden-mssql          Started                                                   9.3s
 ⠿ Container bitwarden-api            Started                                                  16.9s
 ⠿ Container bitwarden-icons          Started                                                  11.3s
 ⠿ Container bitwarden-admin          Started                                                  21.0s
 ⠿ Container bitwarden-portal         Started                                                  22.0s
 ⠿ Container bitwarden-nginx          Started                                                  27.4s
2024.9.1: Pulling from bitwarden/setup
Digest: sha256:dea9de66ef85d21997ec2b096ceea292a37e7d5fda4d73bf50dc9bd565e51308
Status: Image is up to date for bitwarden/setup:2024.9.1
docker.io/bitwarden/setup:2024.9.1
Failed to create CoreCLR, HRESULT: 0x80070008
$

It seems to startup enough where I can still login to my vault via web browser interface.

But… still can not login via iOS app. :frowning:

I do not know if my docker images are being built in compliance to what is in the docker unified folder in GitHub - bitwarden/self-host: Bitwarden's self-hosted release repository.

Any more ideas?

I found this issue on GitHub: bitwarden/setup:2024.2.2 Failed to create CoreCLR, HRESULT: 0x80070008 · Issue #3851 · bitwarden/server · GitHub - That is exactly your issue. Read it for yourself, but I guess, you indeed have to update your docker, because it is too old.

PS: For your mobile app: My tip would be, after you successfully updated your docker and Bitwarden server, then I would completely log out on the iOS app (you seem to already be when you can’t login, but just in case…), deinstall (delete the local data on your iOS device) and reinstall the iOS app. I guess, then you should be able to login again.

1 Like