I’m running a self-hosted Vaultwarden instance behind Traefik Proxy and I’ve hit a really weird issue that I’m struggling to explain.

Setup

• Vaultwarden hosted at 172.29.83.106:11001
• Reverse proxied through Traefik at 172.29.83.243
• Accessible via https://vw.io
• Bitwarden browser extension configured to use my self-hosted Vaultwarden server

The issue

After Chrome has been open for a while, trying to visit https://vw.io in a normal tab starts failing with:

ERR_CONNECTION_TIMED_OUT

But the weird part is:

• curl https://vw.io\ works fine every time
• Incognito mode works fine
• Helium browser (Chromium-based) works fine
• Restarting Chrome temporarily fixes it
• After some time, it breaks again

Things I’ve tested

• Disabled QUIC
• Flushed Chrome socket pools
• Tested HTTP/1.1 vs HTTP/2
• Adjusted Traefik keepalive/timeouts
• Verified Vaultwarden itself is healthy

Chrome DevTools on a failed request just shows:

vw.io (failed) net::ERR_CONNECTION_TIMED_OUT

But in incognito it loads instantly.

What makes this confusing

This feels like either:

• a Chrome-specific bug
• a Bitwarden extension bug
• some weird interaction between the extension and self-hosted Vaultwarden domains

It doesn’t seem like a networking issue because:

• curl works
• other browsers work
• incognito works

Has anyone else run into this with self-hosted Bitwarden/Vaultwarden setups?