I am running version 0.11.0 in a docker container.
It was running all my web apps as a reversproxy perfectly. I changed yesterday this existing working line in Caddyfile sub1.mydomain.de {
with this: sub1.mydomain.de, sub2.mydomain.de {
After saving and restarting container it worked
I could access with both urls.
Today I was not able to connect to any web app from internet. Internal addresses are working.
all logs I checked I found nothing … Any ideas for me how to check the issue?
whitestrake at apollo in ~
❯ env TZ=UTC date
Wed 11 Jul 2018 05:22:42 UTC
whitestrake at apollo in ~
❯ nslookup broehlis.my-wan.de 8.8.8.8
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
Name: broehlis.my-wan.de
Address: 87.123.122.150
whitestrake at apollo in ~
❯ curl -IL http://broehlis.my-wan.de/
curl: (7) Failed to connect to broehlis.my-wan.de port 80: Connection refused
whitestrake at apollo in ~
❯ curl -IL https://broehlis.my-wan.de/
curl: (7) Failed to connect to broehlis.my-wan.de port 443: Connection refused
Seems like something at the edge of the network is refusing connections on web traffic ports.
Firewall and port forwarding configuration is likely the place to look.
Even sitting in the office I found out that the dyndns seems to be not working.
My manual update showed a new IP address.
But when i tried to connect with this new ip adress I was not able to connect either. Yesterdays working port 22 is also not working today …
Can it be an issue with my fritzbox?
Thanks for this hint. I recognized it now too.
I have the feeling my DynDNS service provider is having issues …
This behavior is still existing after a while IP address is changed back. But on both addresses I am not able to reach the server. This is very strange.
That could be what it means. Alternately, it might mean that a firewall is denying access to the port.
Based on the information you’ve given, it seems like the Caddy host is working fine, but your NAT device isn’t working as intended.
Packets received by your router on web ports simply aren’t reaching their intended destination. On its face, the issue is describable as broken port forwarding.
From here, you could try set the Caddy host as a “DMZ host” and see if that works, or swap your NAT device for another, known good device.