I am new to Traefik and got it set up working on docker compose and a couple containers, through docker and external. All that is working fine, but I am unable to get access to the dashboard. I have been digging around for a couple days.
When I put traefik.local into my browser I get: 404 page not found
and with http://192.168.1.5:8080 it's unable to connect.
Port 8080 is free and not connected to any other services.
I think I am missing something. Any help would be appreciated. Thank you!
This does not work. Either traefik.yml file or command: (doc). Here dashboard has no effect.
You did not set insecure for dashboard, so Traefik will not automatically create an entrypoint on 8080. Also you did not publish 8080 with ports: on the container.
If you bind-mounted your traefik.yml file correctly, then Traefik dashboard should be available at http://traefik.local/dashboard/ (on the created entrypoints).
But you need to ensure that traefik.local is resolved via DNS or hosts file to the correct IP. traefik.localhost might work with browser and Traefik on the same machine.
Note that for TLS to be used, it has to be assigned to entrypoint or router, maybe check simple Traefik example.
Note that :ro does not work for sockets, so it has no effect:
Thank you very much for your help. It is VERY confusing for a newbie.
So going through your list
I removed the dashboard from command
added insecure to traefik.yml (traefik.yml OR command: as you mentioned)
added the entrypoint and :8080 to traefik.yml
traefik.local is correctly resolved locally (I can ping traefik.local and it returns the correct IP)
not doing TLS for now
removed :ro
It still doesn't work. I do get a "404 page not found" on traefik.local which I believe means that something is responding vs. when I use the IP nothing happens. I verified that traefik.yml is read since I accidentally had a typo in it and it complained about that, so it is reading it and also the omv.local is working.
I removed the webapi entrypoint in row 7,8 and 19, 20 of the traefik.yml but I still get the 404 error. So you were correct in that it opens something, since I observe literally no change. With that said I still have no access to the webapi.
I just wanted to get it up insecure first since that is easier to set up than going through the whole secure setup introducing way more failure points.
I had it working when I had everything in the docker compose, but in that scenario the external routing isn't possible since that works only with the dynamic configuration. Changing that made the api not work any more and I just can't figure out why.
Well, guess what. I got it to work right now with 3.3.5.
The labels category seems to have fixed it. I just thought I'd give it a try.
I feel like something is redundant, though.
Thank you so much for your help!