Traefik docker rule is not being triggered

Traefik Traefik v3 (latest)
1

Hello,
I have setup Traefik to work with Docker. I have deployed my docker containers for my application, and I can see my docker rule listed in the routers section within the traefik dashboard.

my docker compose file snippet for the frontend service is this:

postiz:
    image: 'ghcr.io/gitroomhq/postiz-app:latest'
    container_name: postiz
    restart: always
    environment:
      MAIN_URL: 'https://kodeazure.com'
      FRONTEND_URL: 'https://kodeazure.com'
      NEXT_PUBLIC_BACKEND_URL: 'https://kodeazure.com/api'
      JWT_SECRET: notshown
      DATABASE_URL: 'postgresql://postiz-user:postiz-password@postiz-postgres:5432/postiz-db-local'
      REDIS_URL: 'redis://postiz-redis:6379'
      BACKEND_INTERNAL_URL: 'http://localhost:3000'
      IS_GENERAL: 'true'
      STORAGE_PROVIDER: local
      UPLOAD_DIRECTORY: /uploads
      NEXT_PUBLIC_UPLOAD_DIRECTORY: /uploads
    volumes:
      - 'postiz-config:/config/'
      - 'postiz-uploads:/uploads/'
    ports:
      - '5000:5000'
    networks:
      - postiz-network
 
      
      
    labels:
      - traefik.enable=true
      - traefik.http.routers.dbjoe.rule=Host(`kodeazure.com`) && PathPrefix(`/`)
      - traefik.http.routers.dbjoe.entryPoints=https
      
    depends_on:
      postiz-postgres:
        condition: service_healthy
      postiz-redis:
        condition: service_healthy

The Traefik Dashboard Rule, that was picked up.

STATUS
success
PROVIDER
docker
RULE
Host(`kodeazure.com`) && PathPrefix(`/`)
NAME
dbjoe@docker
ENTRYPOINTS
https
SERVICE
PRIORITY
40

however when I navigate to 'kodeazure.com' I am presented with the error 'no available server'
I've attached my traefik dashboard.

Screenshot 2025-01-06 195911
Screenshot 2025-01-06 1959111532×880 116 KB

I'm grateful for any assistance.

2

Enable and check Traefik access log in JSON format during a request.

3

Hello,

the below output is the JSON, any further advice?

{
    "ClientAddr": "86.185.182.210:49887",
    "ClientHost": "86.185.182.210",
    "ClientPort": "49887",
    "ClientUsername": "-",
    "DownstreamContentSize": 20,
    "DownstreamStatus": 503,
    "Duration": 45285,
    "GzipRatio": 0,
    "OriginContentSize": 0,
    "OriginDuration": 0,
    "OriginStatus": 0,
    "Overhead": 45285,
    "RequestAddr": "kodeazure.com",
    "RequestContentSize": 0,
    "RequestCount": 1,
    "RequestHost": "kodeazure.com",
    "RequestMethod": "GET",
    "RequestPath": "/",
    "RequestPort": "-",
    "RequestProtocol": "HTTP/2.0",
    "RequestScheme": "https",
    "RetryAttempts": 0,
    "RouterName": "catchall@file",
    "StartLocal": "2025-01-07T18:09:04.638936675Z",
    "StartUTC": "2025-01-07T18:09:04.638936675Z",
    "TLSCipher": "TLS_AES_128_GCM_SHA256",
    "TLSVersion": "1.3",
    "entryPointName": "https",
    "level": "info",
    "msg": "",
    "time": "2025-01-07T18:09:04Z"
}
{
    "ClientAddr": "86.185.182.210:49887",
    "ClientHost": "86.185.182.210",
    "ClientPort": "49887",
    "ClientUsername": "-",
    "DownstreamContentSize": 20,
    "DownstreamStatus": 503,
    "Duration": 54144,
    "GzipRatio": 0,
    "OriginContentSize": 0,
    "OriginDuration": 0,
    "OriginStatus": 0,
    "Overhead": 54144,
    "RequestAddr": "kodeazure.com",
    "RequestContentSize": 0,
    "RequestCount": 2,
    "RequestHost": "kodeazure.com",
    "RequestMethod": "GET",
    "RequestPath": "/favicon.ico",
    "RequestPort": "-",
    "RequestProtocol": "HTTP/2.0",
    "RequestScheme": "https",
    "RetryAttempts": 0,
    "RouterName": "catchall@file",
    "StartLocal": "2025-01-07T18:09:04.841733125Z",
    "StartUTC": "2025-01-07T18:09:04.841733125Z",
    "TLSCipher": "TLS_AES_128_GCM_SHA256",
    "TLSVersion": "1.3",
    "entryPointName": "https",
    "level": "info",
    "msg": "",
    "time": "2025-01-07T18:09:04Z"
}
4

The request to kodeazure.com goes to catchall router, even though dbjoe router has higher priority (higher number), according to dashboard. That is strange. Does dbjoe router or the entrypoint have TLS assigned?

5

Thank you @bluepuma77 issue was I needed to setup the TLS so all is working now.

6

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