wrathek
wrathek
PostsComments
EFPElfHosted / Funky Penguin
Created by wrathek on 12/31/2023 in #🙋┆geek-support
Traefik with containers on different network
(keeping the t2_proxy ip with the original port of 80 gave a tls handshake error)
19 replies
EFPElfHosted / Funky Penguin
Created by wrathek on 12/31/2023 in #🙋┆geek-support
Traefik with containers on different network
AdGuardHome.yaml: 
dns:
  bind_hosts:
    - 192.168.1.25
    - 192.168.30.17
dns:
  bind_hosts:
    - 192.168.1.25
    - 192.168.30.17
19 replies
EFPElfHosted / Funky Penguin
Created by wrathek on 12/31/2023 in #🙋┆geek-support
Traefik with containers on different network
the changes that finally helped, for someone in the future (or myself when the power dying somehow messes this up again): in the dynamic config for adguard: 
  services:
    adguard-svc:
      loadBalancer:
        servers:
          - url: "https://192.168.30.17:443/"
  services:
    adguard-svc:
      loadBalancer:
        servers:
          - url: "https://192.168.30.17:443/"
19 replies
EFPElfHosted / Funky Penguin
Created by wrathek on 12/31/2023 in #🙋┆geek-support
Traefik with containers on different network
as soon as I did that it worked just like it should
19 replies
EFPElfHosted / Funky Penguin
Created by wrathek on 12/31/2023 in #🙋┆geek-support
Traefik with containers on different network
the t2_proxy address was the right rabbithole to chase down. turns out I simply needed to explicitly add that IP to adguard's config, which allows you to assign multiple IPs to listen to
19 replies
EFPElfHosted / Funky Penguin
Created by wrathek on 12/31/2023 in #🙋┆geek-support
Traefik with containers on different network
turns out it WAS a stupid question after all, thank goodness
19 replies
EFPElfHosted / Funky Penguin
Created by wrathek on 12/31/2023 in #🙋┆geek-support
Traefik with containers on different network
here's the log output line I get everytime: 
level=debug msg="'502 Bad Gateway' caused by: dial tcp 192.168.1.25:443: connect: no route to host"
level=debug msg="'502 Bad Gateway' caused by: dial tcp 192.168.1.25:443: connect: no route to host"
19 replies
EFPElfHosted / Funky Penguin
Created by wrathek on 12/31/2023 in #🙋┆geek-support
Traefik with containers on different network
It’s like it knows to route to it, it just doesn’t know how. Is there an equivalent to an overlay network in standalone mode? Or someway to tell one bridge how to route to another?
19 replies
EFPElfHosted / Funky Penguin
Created by wrathek on 12/31/2023 in #🙋┆geek-support
Traefik with containers on different network
Yes sir, the very same
19 replies
EFPElfHosted / Funky Penguin
Created by wrathek on 12/31/2023 in #🙋┆geek-support
Traefik with containers on different network
granted, I have the IP pointed, so... maybe not?
19 replies
EFPElfHosted / Funky Penguin
Created by wrathek on 12/31/2023 in #🙋┆geek-support
Traefik with containers on different network
It can indeed be reached by DNS clients, i have my router pointed at it
19 replies
EFPElfHosted / Funky Penguin
Created by wrathek on 12/31/2023 in #🙋┆geek-support
Traefik with containers on different network
dns.yml = the dynamic config for ad-guard, dsm.yml is an example of one completely external to docker that I have working.
19 replies
EFPElfHosted / Funky Penguin
Created by wrathek on 12/31/2023 in #🙋┆geek-support
Traefik with containers on different network
attching files here, apparently the main one is too much text lol.
19 replies