I feel like I might be missing something but I’m not very familiar with Go or how Caddy works. I feel like it’s an issue with caddy generating the certificate. Do I need to move my domain off of name(dot)com to get it to play nice with caddy?
The browser then tells me the site can’t be reached and that it took too long to respond. But if i revert back to using just http i can access it fine.
The startup message indicates that Caddy is configured correctly to respond to HTTPS requests, and has a valid HTTPS certificate for the site. Combined with the error, the implication is that requests aren’t reaching the HTTPS port.
How do you run Caddy? Is the Caddy host at the edge of the network, or behind NAT?
I do have a router (Apple Airport Extreme if that matters). I’m forwarding port 443 for my server. I also created the proper rules in the Windows Firewall settings. I also tried disabling the firewall altogether. Not sure what else to try.
Nevermind, my dudes. For some reason my router was allowing me to put 2 ips in the same port-forward entry but only actually opening the port for the first entry. I updated it to have only my server IP and now I can get through.
I wasted so much time trying to figure this out and now I feel like a dunce. lol.