Can't get 443 to route to my container

I'm a new user of Docker and Traefik, and I'm having trouble getting port 443 to route to my container (running on Ubuntu 18.04)

The container runs a large executable (FileMaker Sever) which has an admin console on port 443. This container definitely works as expected — if I close Traefik, and run the container with port 443 published, I can get to the admin console without a problem:

version: "3.9"
     container_name: fms-docker
     image: "fms-19-4:final"
       - "443:443"
     privileged: true

However, I'd like to use Traefik to route things, so that I can run more than one instance of the server (not for load-balancing, but to allow two instances of the server on one machine).

My Traefik instance is bound to port 443, Docker is set as a provider, and there is a suitable entrypoint defined in its config file:

    address: :443

The Traefik admin console (port 8080) shows that everything is up and running as expected.

I use Docker Compose to configure the FileMaker container using a yml file:

version: "3.9"
     container_name: fms-docker
     image: "fms-19-4:final"
       - 443
     privileged: true
       - traefik.enable=true
       - traefik.http.routers.Route-WebSecure.rule=Host(``)
       - traefik.http.routers.Route-WebSecure.entrypoints=websecure
       - traefik.http.routers.Route-WebSecure.tls=true
       - traefik.http.routers.Route-WebSecure.service=Service-WebSecure

When I start the container, Traefik detects it, and creates the route websecure->Route-WebSecure->Service-WebSecure using TLS (I can see it on the Traefik console, and there are no warnings)

My problem is that when I try to access, the connection just times out ('Gateway Timeout'). The Docker log files don't show any errors.

Can anyone help me with what I'm doing wrong? I am absolutely flummoxed!

Hi @DrJonJ

I think that these are on different docker networks, more of your compose-files would make certain. Are they in different folder/projects? If they were in the same docker-compose or project they would both be on the same default network.

You can also explicitly declare the network in one or the other compose files and then the other can reference it also.

Hope this helps.


Sorry for the delay — I've been away for a few days.
Thank you so much for this answer.
Yes, this looks like the issue — I must admit, I did not see this at all in the Docker or Traefik guides.
I added a network to Docker:

sudo docker network create -d bridge FMnet

...and then added the network to the Traefik compose file, and each of my FileMaker server compose files, for example:

   fms-19-4-docker :
     container_name: fms-19-4-docker 
     image: "fms-19-4:final"
       - FMnet

     external: true

Now everything is clearly on the same subnet, and the routing works as expected.
Good spot @cakiwi and I hope this answer helps other newbies.



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