Problem using vaultwarden / reverse proxy
Posted: Sat 24. May 2025, 23:58
Hi Guys,
I am trying to bring up vaultwarden via docker. I have therefor created a subdomain under xx.yy.de with the following apache settings
The container ist started with the following docker-compose file:
In the logs of vaultwarden I can see that the webserver is started but no calls are comming in when trying to access xx.yy.de.
I can see that the container is healthy running
Logs of the keyhelp domain
Any idea what might be a problem? Running several other docker container with "same" settings but different ports without any issue.
Thanks in advance
I am trying to bring up vaultwarden via docker. I have therefor created a subdomain under xx.yy.de with the following apache settings
Code: Select all
<IfModule mod_proxy.c>
ProxyPass /.well-known/acme-challenge !
</IfModule>
Alias /.well-known/acme-challenge /home/keyhelp/www/.well-known/acme-challenge
ProxyPass / http://127.0.0.1:8100/ upgrade=websocket
ProxyPassReverse / http://127.0.0.1:8100/Code: Select all
version: '3.3'
services:
vaultwarden:
image: vaultwarden/server:1.33.2
ports:
- '8100:80'
container_name: vaultwarden
restart: always
environment:
DOMAIN: "https://xx.yy.de"
TZ: "Europe/Berlin"
volumes:
- /opt/vaultwarden/vw-data/:/dataI can see that the container is healthy running
Code: Select all
ab559c71fdf7 vaultwarden/server:1.33.2 "/start.sh" About a minute ago Up About a minute (healthy) 0.0.0.0:8100->80/tcp, [::]:8100->80/tcp vaultwardenCode: Select all
(104)Connection reset by peer: [remote xx.xx.xx.xx:60368]AH01102: error reading status line from remote server 127.0.0.1:8100
AH02218: ssl_stapling_init_cert: no OCSP URI in certificate and no SSLStaplingForceURL set [subject: CN=xx.yy.de / issuer: CN=R10,O=Let's Encrypt,C=US / serial: 060A0FCFE3FAF368BB3D86EFC0AB3D214 / notbefore: May 24 20:41:38 2025 GMT / notafter: Aug 22 20:41:37 2025 GMT] Thanks in advance