Traefik proxy not proxying the container after latest update [v2.28.0]

[just5ky]

Description

After the latest update, Traefik proxy is not proxying the container.

Traefik is exposing it properly when i rollback to v2.27.0

Expected behavior
Traefik proxy should detect the container to forward it to a Domain.

What is happening instead?
When I check from Traefik dashboard, it's not listing the container.

Additional context

Docker Compose

services:
  traefik:
    container_name: traefik
    image: traefik
    restart: unless-stopped
    networks:
      - proxy # rename this to your custom docker network
    ports:
      - target: 80
        published: 80
        protocol: tcp
        mode: host
      - target: 443
        published: 443
        protocol: tcp
        mode: host
      - 8080:8080 # Dashboard port
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro # ro = read-only access to the docker.sock
      - $DOCKERDIR/traefik/:/etc/traefik/
    environment:
      CF_DNS_API_TOKEN: $CLOUDFLARE_API_TOKEN
      TZ: $TZ
    extra_hosts:
      - "host.docker.internal:host-gateway"
    labels:
      traefik.http.routers.api.rule: Host(`traefik.$DOMAINNAME`) # Define the subdomain for the traefik dashboard.
      traefik.http.routers.api.entryPoints: https # Set the Traefik entry point.
      traefik.http.routers.api.service: api@internal # Enable Traefik API.
      traefik.http.routers.api.middlewares: auth@file
      traefik.enable: true # Enable Traefik reverse proxy for the Traefik dashboard.

  filebrowser:
    image: filebrowser/filebrowser   #v2.27.0
    container_name: filebrowser
    volumes:
      - "/:/srv"
      - $DOCKERDIR/filebrowser/filebrowser.db:/database.db
      - $DOCKERDIR/filebrowser/settings.json:/config/settings.json
    networks:
      - proxy
    ports:
      - "80:80"
    environment:
      - PUID=$PUID
      - PGID=$PGID
    restart: unless-stopped
    labels:
      traefik.enable: true
      traefik.http.routers.filebrowser.rule: Host(`file.$DOMAINNAME`)
      traefik.http.services.filebrowser.loadbalancer.server.port: 80
      traefik.http.routers.filebrowser.entryPoints: https
      traefik.http.routers.filebrowser.middlewares: auth@file

How to reproduce?
Use the latest version of filebrowser container with traefik proxy.

[2ndwonder]

I have the same issue 😕

[IvanLi-CN]

Me too, looking at the logs it looks like it's only listening on ipv6

Listening on [::]:80

[cerede2000]

Same issue !
I try to find during 1 hour why my filebrowser service not published to traefik and i see this topic !

[robled]

I noticed that the health check is failing when this happens:

May be related to this commit.

[just5ky]

Healthcheck issue #3085

[Zoremeth]

This may be not a fix.

However, for those needing it to work ASAP you can run the docker container with the flag --no-healthcheck.

This disables the health check entirely meaning traefik will pick it up again.

[MMartialis]

same issue. Had to return to previous version until fixed.

[CorySanin]

Healthcheck issue #3085

Yes, this is indeed a duplicate. #3087 should fix it.

[tgrothe]

This may be not a fix.

However, for those needing it to work ASAP you can run the docker container with the flag --no-healthcheck.

This disables the health check entirely meaning traefik will pick it up again.

For docker compose, add:

healthcheck:
  disable: true

https://docs.docker.com/compose/compose-file/compose-file-v3/#healthcheck

then call docker compose up -d again and filebrowser will run... (temporary workaround)

[just5ky]

Closing since given solutions work and its going to be fixed in the next update