Traefik - Funky Penguin's Geek Cookbook

Sorry about the delayed response here - can you show us your Docker .yml definition?


Sure, no problem, it’s below:

version: "3.2"

    image: traefik
    command: --web --docker --docker.swarmmode -- logLevel=DEBUG
      - target: 80
        published: 80
        protocol: tcp
        mode: host
      - target: 443
        published: 443
        protocol: tcp
        mode: host
      - target: 8080
        published: 8080
        protocol: tcp
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - /var/data/config/traefik/traefik.toml:/traefik.toml:ro
      - /var/data/config/traefik/acme.json:/acme.json
      - "traefik.enable=false"
      - public
      mode: global
        constraints: [node.role == manager]
        condition: on-failure

    driver: overlay
      driver: default
      - subnet: is the network segment the physical docker node is on. Not sure if that’s supposed to be my external, internet routable IP… but that is dynamic.

From where I sit, the “dial tcp” errors not able to connect to seem to be the hurdle I’m facing now. FWIW, I setup the registry mirror service too and it also seems to be having trouble connecting to the “docker dns”. This shows up in its logs as well:

panic: Get dial tcp: lookup on read udp> i/o timeout

Okay, yeah, my subnet definition was the problem… I switched the subnet directive to be “” and it looks like traefik was able to start up.

Now I just need to troubleshoot why the let’s encrypt http challenge is not working. :slight_smile:

I believe there is a typo on the yml, it should be --docker.swarmMode instead of --docker.swarmmode this, is true at least for the traefik version I’m using.

Thanks for the recipe.

Ports mapping didn’t work on mac. Here are my changes which could be helpful to run it locally.

    image: traefik
    command: --web --docker --docker.swarmmode --logLevel=DEBUG
      - "80:80/tcp"
      - "443:443/tcp"
      - "8080:8080/tcp"

I keep seeing this message in my docker swarm for traefik. Only using wallabag to test at the moment. And I’ve already been rate limited. :stuck_out_tongue: | time=“2019-03-21T22:56:45Z” level=debug msg=“Filtering container without port, traefik_traefik.1im380tylloon8orfxq5jl7cc: port label is missing, please use traefik.port as default value or define port label for all segments (‘traefik.<segment_name>.port’)”

I had to manually add a DNS name. Which provider is recommended? I can switch to something that works with Traefik. Time to look at docs again.

I like CloudFlare, it works well with Traefik. Can’t speak about the others :slight_smile:

Thanks funkypenguin! Love your work.

1 Like

Running into a wall. just displays a 404. I have not setup oauth in anyway, hopefully it isn’t causing an issue. Any ideas on how to troubleshoot this?

The 404 means you’re talking to Traefik, but Traefik doesn’t know how to route your request. Did you set traefik.port ? (I think it should be 8080)

I just did, and I can see the dashboard but no frontends/backends. Hmm…

If possible is there any chance you are able to join our discord so we can help troubleshoot :slight_smile:

I can confirm NAMECHEAP works fine with Traefik too – even the wildcard DNS challenge – BUT – they don’t unlock the API key for that until you’ve spent like $50 with them. Woth it if you like their domain hosting prices and are comfortable locking in a longer purchase.


Just wanted to mention that the instructions say

Create /var/data/config/traefik/traefik.yml as follows:

And then tell you to

create an overlay network by running
docker stack deploy traefik -c /var/data/traefik/traefik.yml

Is that an extra ‘config’ or a missing ‘config’? It’s arbitrary because you just adjust the paths accordingly but I thought I’d mention it.


Also the scratch stack sets up a network named “public” with a specific subnet, but then it is never used by the examples that follow. The traefik network is named traefik_public, which of course would not exist yet, so it is created anyways.

I keep receiving the following in an email when utilizing github and traefik:

On February 15th, 2020 at 04:23 (UTC) your application (Radarr) used an access token (with the User-Agent Go-http-client/1.1) as part of a query parameter to access an endpoint through the GitHub API:

Please use the Authorization HTTP header instead as using the access_token query parameter is deprecated

What should I be looking to do to resolve this?


I’m getting an error nobody has flagged so far, from what I can tell.

I reach this point:

$ docker stack deploy traefik-app -c /var/data/config/traefik/traefik-app.yml
Creating service traefik-app_traefik

So far, so good.

But then $ docker stack ps traefik-app returns lots of failed containers (well, the same failed container, starting over and over), with the error message "task: non-zero exit (1)" against each one.

So then $ docker services logs {id of one of the failed containers} tells me:

command traefik error: field not found, node: redirect

I little Googling of “field not found, node: redirect” brings up a few examples of where this is happening because of a mismatch of traefik v1 and v2 configs, ie. trying to use a traefik v1 config with traefik >v2.0

Is that what’s happening here?

I should also point out that I’m running this on a one-node swarm, but if adding more nodes would be worth trying, I’ll give that go.


Welcome @Matthew_Lancey! Yes, I’d be inclined to agree with you on that. A quick test would be trying to run Traefik v1, and seeing whether that solves the problem. There are several geeks in our Discord server, who’ve successfully migrated to Traefik v2, and a v2 recipe is in the works - you could pop in there and get some pointers? (Specifically @HexF is using it, I’m aware…)

Cool - so for those following along at home, I changed traefik-app.yml as follows and the issue went away:

image: traefik:1.7

Thanks @Matthew_Lancey, that tip fixed the errors I was having trying to deploy Traefik as well. Cheers!