[GH-ISSUE #49] Unable to use with reverse proxy (letsencrypt by linuxserver.io) #21

New issue

Closed

opened 2026-03-03 01:23:49 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 01:23:49 +03:00

Owner

Originally created by @Ryonez on GitHub (Jul 1, 2018).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/49

Hi there.

I've been working on this for a few hours now and I'm makeing no headway.
I'm trying to to use the letsencrypt docker by linuxserver.io to serve bitwarden_rs over https to the internet.

It's all set up, the url is redirected from http to https if needed, and the proxy forwards the traffic to the http port on the bitwarden docker. However any attempt to load the page returns with ERR_CONNECTION_CLOSED

There doesn't seem to be anything happening, the dev interface for chrome says that it stalled.

Any change for some help please?

Originally created by @Ryonez on GitHub (Jul 1, 2018). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/49 Hi there. I've been working on this for a few hours now and I'm makeing no headway. I'm trying to to use the letsencrypt docker by linuxserver.io to serve bitwarden_rs over https to the internet. It's all set up, the url is redirected from http to https if needed, and the proxy forwards the traffic to the http port on the bitwarden docker. However any attempt to load the page returns with `ERR_CONNECTION_CLOSED` There doesn't seem to be anything happening, the dev interface for chrome says that it stalled. Any change for some help please?

kerem closed this issue

2026-03-03 01:23:49 +03:00

kerem commented

2026-03-03 01:23:50 +03:00

Author

Owner

@Ryonez commented on GitHub (Jul 1, 2018):

Alright, turns out it was my fault.

Turns out the nginx has to load the default site config file first. I had named the bitwarden config bitwarden, which placed it above default in the load order. The things you learn huh >.<

@Ryonez commented on GitHub (Jul 1, 2018): Alright, turns out it was my fault. Turns out the nginx has to load the default site config file first. I had named the bitwarden config `bitwarden`, which placed it above `default` in the load order. The things you learn huh >.<

kerem referenced this issue

2026-03-03 02:19:55 +03:00

[PR #39] [MERGED] Update Vault to 1.27.0 #2588