▲ 26 ▼ [SOLVED] Caddy and multiple subdomains/reverse proxies (lemmy.dbzer0.com) submitted 2 weeks ago by UnrefinedChihuahua@lemmy.dbzer0.com to c/selfhosted@lemmy.world 10 comments fedilink hide all child comments Hoping the brain trust can help. Single reverse proxy? No issues at all. If I add multiple per some instructions on the caddy forums, nothing works - the docker container just continually reboots with no errors in the log. Caddyfile: fmd.domain.ca { reverse_proxy 10.179.200.199:8080 } llama.domain.ca { reverse_proxy 192.168.3.199:3000 ) With only the fmd entry, works fine.
[–] UnrefinedChihuahua@lemmy.dbzer0.com [S] 26 points 2 weeks ago (4 children) Idiot. Didn't close the last bracket and instead used a parentheses. D'oh! Working as it should with the correction. permalink fedilink source hideshow 4 child comments replies: [–] cybervseas@lemmy.world 26 points 2 weeks ago (1 child) For once it wasn't DNS! 🔥🔥 permalink fedilink source parent hideshow 1 child comment replies: [–] curbstickle_lw@lemmy.world 10 points 2 weeks ago Its never DNS! Unless it is, which is almost always. permalink fedilink source parent [–] lemmyvore@feddit.nl 9 points 2 weeks ago (1 child) It's a good idea to validate your config before reloading it (whether it's by running caddy reload or restarting/reprovisioning the container): [docker exec -it caddy-container] caddy validate --config /etc/caddy/Caddyfile permalink fedilink source parent hideshow 1 child comment replies: [–] UnrefinedChihuahua@lemmy.dbzer0.com [S] 7 points 2 weeks ago This is a home lab, I have no change control or testing. It either comes up or it doesn't. We test in prod around here. One day it's gonna bite me in the ass hard. permalink fedilink source parent
[–] cybervseas@lemmy.world 26 points 2 weeks ago (1 child) For once it wasn't DNS! 🔥🔥 permalink fedilink source parent hideshow 1 child comment replies: [–] curbstickle_lw@lemmy.world 10 points 2 weeks ago Its never DNS! Unless it is, which is almost always. permalink fedilink source parent
[–] curbstickle_lw@lemmy.world 10 points 2 weeks ago Its never DNS! Unless it is, which is almost always. permalink fedilink source parent
[–] lemmyvore@feddit.nl 9 points 2 weeks ago (1 child) It's a good idea to validate your config before reloading it (whether it's by running caddy reload or restarting/reprovisioning the container): [docker exec -it caddy-container] caddy validate --config /etc/caddy/Caddyfile permalink fedilink source parent hideshow 1 child comment replies: [–] UnrefinedChihuahua@lemmy.dbzer0.com [S] 7 points 2 weeks ago This is a home lab, I have no change control or testing. It either comes up or it doesn't. We test in prod around here. One day it's gonna bite me in the ass hard. permalink fedilink source parent
[–] UnrefinedChihuahua@lemmy.dbzer0.com [S] 7 points 2 weeks ago This is a home lab, I have no change control or testing. It either comes up or it doesn't. We test in prod around here. One day it's gonna bite me in the ass hard. permalink fedilink source parent