Listening on a specific interface (or IP address) #5292
-
How does one get vaultwarden to listen on a chosen network interface? or more precisely, listen on a specific IP address. Network interfaces are assigned distinct IP addresses. Programs listen through an interface by binding a socket to the IP address associated with the interface. Vaultwarden has no configuration option for choosing the IP address it binds to. instead it expects a Domain name. how does that work ? vaultwarden has to bind to an IP address at some point. the TCP protocol has no notion of domains. Does vaultwarden resolve the domain through DNS at startup then bind to the resolved IP address? if so, would it be sufficient to add a new domain name in |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Vaultwarden uses the Rocket framework. In the container we set the address to vaultwarden/docker/Dockerfile.debian Lines 171 to 172 in 9cd400d If you run it locally it will bind to the Rocket defaults instead. |
Beta Was this translation helpful? Give feedback.
Vaultwarden uses the Rocket framework. In the container we set the address to
0.0.0.0
and the port to80
:vaultwarden/docker/Dockerfile.debian
Lines 171 to 172 in 9cd400d
If you run it locally it will bind to the Rocket defaults instead.
[2024-12-14 06:41:18.045][start][INFO] Rocket has launched from http://127.0.0.1:8000