Issues after Docker 26.1.3 update

[seal-82]

Hi everybody,

after update to Docker-CE 26.1.3 I ran into issues with my vaultwarden. In my setup behind a traefik proxy, it suddenly threw the error 502 bad gateway. After rollback to docker 26.1.2, everything is back to normal.

Vaultwarden logs didnt show any errors.

Anybody else affected by this issue?

[BlackDex]

I'm running the same version, but do not seem to have an issue.
I would suggest to check the reverse proxy logs too, and the information of docker ps if that shows something.

[seal-82]

Thanks for your feedback. I checked traefik status website. There I did not get any errors. Will check all the logs and investigate further after my vacation. But maybe it is related to docker 26.1.3 in combination with traefik 3.0.0...

[BlackDex]

It could be that, or something changed in the networking. But that works be strange in a patch release of docker though

[snowp0p]

Hi, i'm experiencing the same issue (502 bad gateway)
Running with omv 7, docker 26.1.3 and Swag reverse proxy
In Swag dashboard, i only notice : http://vaultwarden:80/ not available (but the container is running healthy in portainer).

[seal-82]

Good to know I'm not the only one 😊 vaultwarden container also gives me status healthy and in traefik dashboard there is no error...

[TaisukeIto]

Hi everybody,

after update to Docker-CE 26.1.3 I ran into issues with my vaultwarden. In my setup behind a traefik proxy, it suddenly threw the error 502 bad gateway. After rollback to docker 26.1.2, everything is back to normal.

Vaultwarden logs didnt show any errors.

Anybody else affected by this issue?

Me too.
after update to Docker-CE 26.1.3 I ran into issues

[clemone210]

I had this too.
I had to change the port to 80 instead of 88 which is exposed.
So I have it with Cloudflare Tunnel and before I had vaultwarden:88 in my tunnel config, after a change to vaultwarden:80 it works again.

[seal-82]

wanted to give you an update on the topic. After upgrade to current docker-sts version, access to vaultwarden is possible again. I'm not really sure what was the issue. But I'm happy to have vaultwarden working again with latest docker verion :-)