Nvm, I was stupid, not running updateself first. Issue disappeared on server v2025.8
1 Like
Thanks for claryfying. My fault was that I assumed that ghrc(.)io/bitwarden/self-host:latest will give the latest release. Pity, self-host marked latest is 2025.2.2, I pushed 2025.8.1-beta and it works now.
1 Like
That url appears to be a malicious typosquat on ghcr.io.
I see it mentioned subtly but for those who didn’t catch it, the unified self hosted (beta) changed repos so make sure your compose file is pointing to the new ghcr repo. I was on version 2025.3 lol, 2025.8 fixed my issue.
6 Likes
We’re having troubles with the same error. We had the server 2024.3 and updated to 2025.8.0 after reading this post. Still having troubles to log in using web-browser (Chrome and Brave), through web-portal and extension. (Cannot read properties of undefined (reading ‘toLowerCase’))
How can we solve the issue? I don’t have service: bitwarden in docker-compose.yml so I can’t change ghrc(.)io/bitwarden/self-host: to beta…
Thanks in advance,
same case, self hosted.
Bitwarden Selfhosted Server 2024.6.1
Windows 10 22h2, Chrome Version 139.0.7258.155, Bitwarden Extension 2025.8.2 Work OK
Windows 11 24h2 IoT LTSC, Chrome Version 139.0.7258.155, Bitwarden Extension 2025.8.2 Error
Android 15 Work Ok
same prob: login to updated chrome & firefox exten with “self hosted”
any idea to solve the problem???
Hi all, please update your server to ensure your sever and client version match, and review this thread: Self-Hosting Update: Migration to GitHub Container Registry
Hello,
I have a problem because in this week i back to work and i try to use my self-hosted bitwarden on synology. I create this instance in 2023r, using way describing on mariushosting blog. I don’t updated this instance while 2023, and when i try to use and i got a message: “cannot read properties of undefined” (reading to tolowercase)” i try to find information about it and I found information that i should update it, i try to update using portainer and option “Recreate” with parameter Re-pull image, everything finish successful but now I can’t login to my vault. When i try to login i have a info “Wystąpił błąd. Wystąpił nieoczekiwany błąd” and option forgot password doesn’t work and gave a message Wystąpił błąd. An unhandled server error has occurred. and when i check info about connection i have a message: “Status Code 500 Internal Server Error” Here is my admin.log and info about docker container:
Can I do it something?
I have still the same problem with the Bitwarden Desktop App (!) under Windows and the Chrome Extension - all versions are up to date and the latest docker image is running!
Which server version is that exactly?
This is what is says after updating the image twice now using this method Synology: How to Update Your Docker Containers Using Portainer – Marius Hosting :
Version
Server Installed
2025.2.3
Server Latest
2025.8.1
Web Installed
2025.2.2
Web Latest
2025.8.2
@CarnivoreD Okay, so you are not running the latest versions. – Did you see this info: Self-Hosting Update: Migration to GitHub Container Registry ?
But this is the latest not the beta?!?
I redeployed it with the beta and now it say:
Version
Server Installed
2025.8.1
Server Latest
2025.8.1
Web Installed
2025.8.0
Web Latest
2025.8.2
…and works.
Thank you very much…!
1 Like
This Is my configuration and everything works fine:
Web extension 2025.8.2
Desktop version 2025.8.2
Server version (self-hosted) 2025.8.1
But what I do find strange is, when I open up my browser to my bitwarden self hosted URL
I see version 2025.8.0 below and my server what I mentioned is 2025.8.1
But it still work though…
If I understand you correctly, then that shows your “web vault / web app” version.
Do you mean the browser extension? Because if that should be the web vault version, then that would be in conflict with showing 2025.8.0 in the browser…
Yes, I meant my web vault version. Ah ok I see