IPv6 and Docker

I get IPv6 from my ISP and was wondering if it would be possible to assign IPv6 to the jvb container to eliminate the need of STUN/TURN for people connecting over IPv6

My setup is configured like this:

  • Domain names with A and AAAA-records set
  • Apache reverse proxy to docker and that does SSL
  • docker-jitsi-meet with:
    DOCKER_HOST_ADDRESS for IPv4 connectivity behind NAT

What I think that needs to be done:

  • in web/config.js: useIPv6: true,
  • in web/nginx/meet.conf: Comment out proxy_set_header X-Forwarded-For $remote_addr; to pass the correct remote as Apache sets this earlier in the chain.
  • Follow https://docs.docker.com/config/daemon/ipv6/ and enable IPv6 for at least jvb
  • Setting some SRV records?

Does anybody have some additions? I am able to freely test in my environment whatever you suggest.

1 Like

When you set a AAAA-record now (to web), the iOS jitsi client does not connect as it probably tries to connect directly to UDP10000 or TCP4443.
This supports my idea that we need some additional SRV or sub-records for the connection to jvb-container to work.

If the clients don’t check any other records and there isn’t a way to set alternative addresses for jvb externally, I think it is safe to say docker-jitsi-meet can’t work with IPv6 (without dirty IPv6 NAT).
Should I consider switching to the debian jitsi packages?

Interesting topic. Which solution do you use now?

I run jitsi-meet outside of docker on my debian host.