Docker does not listen on IPv6 connections #1716

New Issue

MrUnknownDE · 2026-04-06T02:16:49+02:00

MrUnknownDE commented

2026-04-06 02:16:49 +02:00

Originally created by @MaZe3D on 3/4/2023

Subject of the issue

I 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.

Install method: Docker Image
Other relevant details:
Container running with a IPv6 Address directly assigned from a ipv6-capable network.

Steps to reproduce

Run the container with a IPv6 address assigned.
Try to connect to the web-interface with this address
You cannot access the web-interface

Expected behaviour

The Web-Interface should be accessible from a docker with IPv6 address.

Actual behaviour

The Web-Interface is not accessible via IPv6 address.

Troubleshooting data

I can ping the container with an IPv6-Address assigned. My Docker command to run it:

docker run
  -d
  --name='vaultwarden'
  --net='br0.69'
  --ip='10.69.69.69'
  --ip6='fd00:59fb:c27b:3e0e:d6c6:ad5d:2b33:b44b'
  -e TZ="OBFUSCATED"
  -e HOST_OS="OBFUSCATED"
  -e HOST_HOSTNAME="OBFUSCATED"
  -e HOST_CONTAINERNAME="vaultwarden"
  -e 'TCP_PORT_80'='80'
  -e 'SERVER_ADMIN_EMAIL'='OBFUSCATED'
  -e 'SIGNUPS_ALLOWED'='true'
  -e 'INVITATIONS_ALLOWED'='true'
  -e 'WEBSOCKET_ENABLED'='true'
  -e 'ADMIN_TOKEN'='OBFUSCATED'
  -v 'OBFUSCATED':'/data':'rw' 'vaultwarden/server:latest'

(I replaced both IPv4 and IPv6 with dummy addresses and obfuscated everything that is unnecessary with OBFUSCATED).

Thanks for reading and have a lovely day!

*Originally created by @MaZe3D on 3/4/2023*   ### Subject of the issue  I 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.  * Install method: Docker Image * Other relevant details: Container running with a IPv6 Address directly assigned from a ipv6-capable network. ### Steps to reproduce  1. Run the container with a IPv6 address assigned. 2. Try to connect to the web-interface with this address 3. You cannot access the web-interface ### Expected behaviour  The Web-Interface should be accessible from a docker with IPv6 address. ### Actual behaviour  The Web-Interface is not accessible via IPv6 address. ### Troubleshooting data  I can ping the container with an IPv6-Address assigned. My Docker command to run it: ``` docker run -d --name='vaultwarden' --net='br0.69' --ip='10.69.69.69' --ip6='fd00:59fb:c27b:3e0e:d6c6:ad5d:2b33:b44b' -e TZ="OBFUSCATED" -e HOST_OS="OBFUSCATED" -e HOST_HOSTNAME="OBFUSCATED" -e HOST_CONTAINERNAME="vaultwarden" -e 'TCP_PORT_80'='80' -e 'SERVER_ADMIN_EMAIL'='OBFUSCATED' -e 'SIGNUPS_ALLOWED'='true' -e 'INVITATIONS_ALLOWED'='true' -e 'WEBSOCKET_ENABLED'='true' -e 'ADMIN_TOKEN'='OBFUSCATED' -v 'OBFUSCATED':'/data':'rw' 'vaultwarden/server:latest' ``` (I replaced both IPv4 and IPv6 with dummy addresses and obfuscated everything that is unnecessary with `OBFUSCATED`). Thanks for reading and have a lovely day!

MrUnknownDE closed this issue

2026-04-06 02:16:49 +02:00

Sign in to join this conversation.

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/vaultwarden#1716