wrathek
EFPElfHosted / Funky Penguin
•Created by wrathek on 12/31/2023 in #🙋┆geek-support
Traefik with containers on different network
I KNOW this has to be a dumb question, but I've been banging my head against the wall for days trying to get this to work.
TL;DR, I have traefik running just fine for everything but my instance of adguard home, which I have on a vlan in host mode. When trying to connect to dns.website, traefik tells me "no route to host" on the IP (which I have defined in a dynamic configuration, so it knows the exact static IP & port).
The reason this is driving me so insane, is I had this working 100% flawlessly, up until my server lost power a few days ago. Now, no matter what I do, I cannot get it to route correctly anymore.
I've tried the obvious like adding adguard to the t2_proxy network that traefik and all other containers are on, via portainer, but then traefik gives a "connection refused" error when trying to route to the IP assigned in the proxy network. (Perhaps this is the correct route to chase down, but I'm just not sure what else to do to fix it).
I've also tried adding traefik to the vlan in addition to t2_proxy, but then traefik FREAKS and I have to completely stop it and remove it from the container before anything works again.
Please help! Nothing on the internet is leading me to a solution, and trust me, I've researched for literal hours every single day.
yml's incoming next, post is too long.
19 replies