Traefik issues in docker swarm
I have a docker swarm using gkoerks old method https://github.com/gkoerk/QNAP-Docker-Swarm-Setup running plex, autopirate, hass, traefik. Static DNS via cloudflare. I believe my qnap went through an automatic update to QTS 5.1.4.2596 tonight. It has been for the previous 3 years.
I suddenly am unable to access my stuff.
The containers are running in in container station but I can't access them via dns or via static server ports.
Error output in traefik.log
GitHub
GitHub - gkoerk/QNAP-Docker-Swarm-Setup: A guide for configuring th...
A guide for configuring the docker swarm stack on QNAP devices with Container Station - GitHub - gkoerk/QNAP-Docker-Swarm-Setup: A guide for configuring the docker swarm stack on QNAP devices with ...
6 Replies
Through the asssistance of another user I've attempted to update pt 3 /opt/etc/profile to change docker-compose to docker compose of gkoerks guide.
We've checked and recreated the network for swarm.
Traefik appears to be set up correctly according the person that has assisted me.
- "traefik.http.routers.traefik.service: api@internal"
That should be =
not :
- "traefik.http.routers.traefik.service=api@internal"
@AustinYQM Thank you for the reply! That actually solved the error in the log, but this previous version has functioned. I'm guessing qnap must have broken something because it still doesn't work.
Could have also been a change to docker engine that effected how it parsed the yaml.
Not sure if the QTS update brought a Docker Engine update.
I'm unsure. I know that certain commands have been updated but my start up scripts are updated to reflect some changes ie docker-compose -> docker compose. Right now I can run traefik but I can't access it internally or externally
My inability to access my swarm is related to the update, but not sure on what changed. Change log doesn't reflect docker engine update.
Change the Traefik logging level to debug, it will spit out (much much) more and might be helpful.
Are you using proxies on your DNS via cloudflare, are you sure the whitelist is complete?