coolify: [Bug]: Traefik dynamic setup not working
Description
I just followed docs here and it ask me for the basic auth credentials but when I enter those it throws a 404 page. I think it is not quite getting to the service api@internal or something.
Minimal Reproduction (if possible, example repository)
Enter the following *.yml file into the Dynamic Configurations for the proxy of your server. Assuming the IP of your server is 10.0.0.37. Password is the same as the docs test test
http:
routers:
dashboard:
rule: Host(`10.0.0.37.sslip.io`) && (PathPrefix(`/dashboard`) || PathPrefix(`/api`))
service: api@internal
middlewares:
- auth
middlewares:
auth:
basicAuth:
users:
- "test:$apr1$154ethlp$Re.R1QjCkyOyKKmgYHHYP1"
Bonus: (Not a blocker)
When entering the contents of the *.yml file the first time it throws an error about base64 encode and it enters the file as empty which then you can proceed to hit the Edit button and enter the contents of that file right there.
Exception or Error
No response
Version
v4.0.0-beta.239
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 9
- Comments: 18 (1 by maintainers)
I initially had the same issue of getting a 404 page when trying to access the dashboard, but I eventually got it working after doing a few things.
Firstly, my domain for the dashboard is set up in Cloudflare with strict TLS, and going to the URL showed an error page related to an invalid SSL cert. To fix it, I added the following line to the dynamic config file.
Secondly, and this is the most important part, I ADDED A TRAILING SLASH TO MY URL. For whatever reason, it is MANDATORY. Instead of going to
https://example.com/dashboard, you have to go tohttps://example.com/dashboard/https://doc.traefik.io/traefik/operations/dashboard/#the-dashboard
My dynamic configuration file is named
dashboard.yamland looks like this (edited to take out sensitive details):In my case, anytime I restart the proxy, I get a 404 when accessing the Coolify dashboard. The websites and the other services are working, though.
Thanks this was the same approach I eventually figured out that worked. Perhaps it might be possible to start the proxy again by listing the containers that are not running using “docker ps -a” and then starting it from there. But yeah the problem arose because I tried to restart the proxy in the hope that the traefik dashboard would work so I could gain some visibility into the networking. Perhaps there is a tool to visualize the entire docker internal networking and traefik in a dependency map?
@Trubador I ran into a similar issue before, and I think I fixed it by restarting the proxy. If you ssh into the relevant server, what do you see when you run
docker psorsudo docker ps? If the proxy is running, you should see a running container with the namecoolify-proxy. If Coolify itself is running, there would also be a container with the namecoolify.I don’t remember whether I found a way to start the proxy programmatically. I would have to look through the Coolify codebase to figure that out. However, I think I was able to start the proxy by doing the following steps:
http://123.456.789:8000)