Traefik dosen't bind IPv6 ports

Traefik Traefik v2 (latest)
1

Hi,

yesterday i recognized that Traefik dosen't bind the IPv6 ports of my entry points (80,443)

when use netstat -an I get

Proto Recv-Q Send-Q Local Address           Foreign Address         State      
tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN     
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN     
tcp        0      0 0.0.0.0:113             0.0.0.0:*               LISTEN     
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN     
tcp6       0      0 :::113                  :::*                          LISTEN     
tcp6       0      0 :::22                    :::*                          LISTEN

port 80 and 443 should also be listet as tcp6.

traefik.toml:

[log]
  level = "INFO"

[providers.docker]
  exposedByDefault = false
  endpoint = "unix:///var/run/docker.sock"

[providers.file]
  directory = "/tls/" 

[api]
  dashboard = false
  debug = false
  insecure = false

[entryPoints]
  [entryPoints.web]
    address = ":80"
  [entryPoints.web-secure]
    address = ":443"
 



[certificatesResolvers]
  [certificatesResolvers.default.acme]
    email = "sonic@dersonic.org"
    storage = "acme.json"
    [certificatesResolvers.default.acme.tlsChallenge]

docker-compose.yml:

version: '3.6'

services:
    

    traefik:
        image: traefik:latest
        command: --configFile=/traefik.toml
        restart: unless-stopped
        ports:
            - "80:80"
            - "443:443"
#           - "8080:8080"
        volumes:
            - /var/run/docker.sock:/var/run/docker.sock
            - /opt/traefik/traefik.toml:/traefik.toml
            - /opt/traefik/acme.json:/acme.json
            - /opt/traefik/tls:/tls
        networks:    
            traefik:

networks:
        traefik:

Thanks for your time!

2

I found a solution.

The problem is docker version 20.10.2.
I downgrade to 20.10.1 which work without problems.

3

I do have the exact same problem. Retrieving certificates with IPv6 DNS does not work and results in ACME challenge error 400. Only providing IPv4 in the DNS and the challenge runs without problems.

P.S. or downgrade docker. according to github the problem will be fixed.

4

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.