App running at 8444 cannot be accessed through Traefik

[nanikjava]

Hi,

I have a simple Go http server with the following Dockerfile

FROM golang:1.22-alpine

RUN apk update && apk upgrade && \
    apk add --no-cache bash git openssh

WORKDIR /app

COPY go.mod go.sum ./

RUN go mod download

COPY . .

RUN go build -o main .

EXPOSE 8444

CMD ["./main"]

and docker-compose.yaml

version: '3'

services:
  app:
    build:
      context: . 
      dockerfile: Dockerfile
    ports:
      - "8444:8444" 
    restart: unless-stopped
    networks: 
      - backend

networks:
  backend:    
    driver: bridge   

The Target is configured as below

The Application is configured as below

The deployment is successful and can see Traefik and the server container deployed, docker ps shows it

CONTAINER ID   IMAGE                                                     COMMAND                  CREATED          STATUS          PORTS                                       NAMES
503c876a83b9   simpleserver-2mylywuuquxqzqfxf2e8rjepfhr/app:production   "./main"                 54 minutes ago   Up 54 minutes   8444/tcp                                    simpleserver-production-2mylywuuquxqzqfxf2e8rjepfhr-app-1
5bf226824b68   traefik:v2.11                                             "/entrypoint.sh --en…"   54 minutes ago   Up 54 minutes   0.0.0.0:80->80/tcp, :::80->80/tcp           seelf-internal-2mylvhufdh3a9qhl0orkwf5ajaq-proxy-1

The problem is when accessing it from other PC via http://192.168.1.6 not getting response from the app but getting

404 page not found

which looks like coming from Traefik.

Here are lables info from docker inspect of the server

"Labels": {
                "app.seelf.application": "2mYlyWuUQUXQzqFXf2E8RJepFHr",
                "app.seelf.environment": "production",
                "app.seelf.subdomain": "simpleserver",
                "app.seelf.target": "2mYlvHufDh3a9QHL0ORKwf5aJAQ",
                "com.docker.compose.config-hash": "99051eb456a04278414ffb8ae500a160b7311f081dd21fe9bdb2b844e937d987",
                "com.docker.compose.container-number": "1",
                "com.docker.compose.depends_on": "",
                "com.docker.compose.image": "sha256:e059dfc9e5d931f6b7f62d2c77ec2b75e4755c4b21e958d4957f1d0e74d93a30",
                "com.docker.compose.oneoff": "False",
                "com.docker.compose.project": "simpleserver-production-2mylywuuquxqzqfxf2e8rjepfhr",
                "com.docker.compose.project.config_files": "/home/nanik/GolandProjects/seelf/data/apps/2mYlyWuUQUXQzqFXf2E8RJepFHr/production/docker-compose.yaml",
                "com.docker.compose.project.working_dir": "/home/nanik/GolandProjects/seelf/data/apps/2mYlyWuUQUXQzqFXf2E8RJepFHr/production",
                "com.docker.compose.service": "app",
                "com.docker.compose.version": "",
                "traefik.http.routers.simpleserver-production-2mylywuuquxqzqfxf2e8rjepfhr-app-8444-http.entrypoints": "http",
                "traefik.http.routers.simpleserver-production-2mylywuuquxqzqfxf2e8rjepfhr-app-8444-http.service": "simpleserver-production-2mylywuuquxqzqfxf2e8rjepfhr-app-8444-http",
                "traefik.http.services.simpleserver-production-2mylywuuquxqzqfxf2e8rjepfhr-app-8444-http.loadbalancer.server.port": "8444"
            }

[YuukanOO]

As stated in the target's URL help message and in the panel on the application page, services will be exposed as subdomains on the target's url. So in your example, if your application is named simpleserver, it will be available at http://simpleserver.192.168.1.6, but you should use a DNS here, http://docker.localhost for example.

[nanikjava]

Thanks @YuukanOO. After adding simpleserver.192.168.1.6 to my local DNS server it was able to access the app.

What kind of DNS setup would be sufficient for local network ?. Planning to set it up for 3 of my server.

[YuukanOO]

Maybe adding a wildcard rule to forward everything to where the traefik proxy is hosted (192.168.1.6 in your example)?