I recently logged out of my self-hosted bitwarden instance, (via the chrome extension), and then have found myself unable to log back in again.
I think it is related to a docker desktop update in the last couple of weeks.
Now, if I try to log in, I just get ‘failed to fetch’. If I check the docker containers, the bitwarden-nginx one is restarting constantly with the log:
2023-01-03 13:53:20 nginx: [emerg] host not found in upstream “web” in /etc/nginx/conf.d/default.conf:36
Any ideas? Currently can’t access my passwords!
Hi @shifty.powers79 - what version of Bitwarden server are you running? My guess is that it may be deprecated and needs updating to work with the latest clients. See here:
Although, that error message suggests you may have multiple issues. If you execute docker ps on the host, are all the other containers healthy?
" bitwarden.sh version 2022.12.0
Docker version 20.10.21, build baeda1f
Docker Compose version v2.13.0"
I currently can’t update, as it complains that
“no such service: web”
And yes, all the other containers are showing as healthy
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
e39516bd8ba7 bitwarden/nginx:2022.12.0 "/entrypoint.sh" 13 days ago Restarting (1) 11 seconds ago bitwarden-nginx
068dc0ed25d3 bitwarden/admin:2022.12.0 "/entrypoint.sh" 13 days ago Up About a minute (health: starting) 5000/tcp bitwarden-admin
9f457204f83c bitwarden/api:2022.12.0 "/entrypoint.sh" 13 days ago Up About an hour (healthy) 5000/tcp bitwarden-api
79c89bc0438a bitwarden/sso:2022.12.0 "/entrypoint.sh" 13 days ago Up About an hour (unhealthy) 5000/tcp bitwarden-sso
08e60095b1a3 bitwarden/events:2022.12.0 "/entrypoint.sh" 13 days ago Up About an hour (healthy) 5000/tcp bitwarden-events
df8faf582474 bitwarden/attachments:2022.12.0 "/entrypoint.sh" 13 days ago Up About an hour (healthy) bitwarden-attachments
b3584e33ec12 bitwarden/icons:2022.12.0 "/entrypoint.sh" 13 days ago Up About an hour (healthy) 5000/tcp bitwarden-icons
d21303753d9e bitwarden/notifications:2022.12.0 "/entrypoint.sh" 13 days ago Up About an hour (healthy) 5000/tcp bitwarden-notifications```
After all of that, I used the command:
And it restarted and worked fine. Very strange.
Well, I am glad that was an easy fix. I had noticed in your last post that your admin container looked like it was also in a state where it was restarting constantly, too, and was about to suggest a full restart.