-
Subject of the issueI am migrating my network to IPv6 only operation. Target of this is that my reverse proxy only accesses my services with a IPv6 only connection. While having great success migrating most of my containers (like mariadb, postgresql, nextcloud and some others), vaultwarden is the only one that won't listen on IPv6-addresses. I tested the connection to the container, both IPv4 and Ipv6 are pingable, but the web-interface is only reachable via IPv4.
Steps to reproduce
Expected behaviourThe Web-Interface should be accessible from a docker with IPv6 address. Actual behaviourThe Web-Interface is not accessible via IPv6 address. Troubleshooting dataI can ping the container with an IPv6-Address assigned. My Docker command to run it:
(I replaced both IPv4 and IPv6 with dummy addresses and obfuscated everything that is unnecessary with Thanks for reading and have a lovely day! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
You need to set te following variables to get it to work. ROCKET_ADDRESS=::0
WEBSOCKET_ADDRESS=::0 |
Beta Was this translation helpful? Give feedback.
You need to set te following variables to get it to work.