caddy -validate
Activating privacy features... done.
Serving HTTPS on port 443
https://federicod.dev
Serving HTTP on port 80
http://federicod.dev
WARNING: File descriptor limit 1024 is too low for production servers. At least 8192 is recommended. Fix with `ulimit -n 8192`.
In between each try I didn’t left caddy running so it’s ok that you had a connection refused.
There is port forwarding enabled 80-80 443-443 and there aren’t proxies. Both ports are forwarded to a proxmox host.
One last try I did was to swap out the domain name with the public IP and TLS off and the test page was served correctly.
publicip:80 {
root ...
tls off
}
EDIT
I did leave the caddy service running in case you needed to further inspect the issue by querying the domain.
I also doubted my DNS configuration over Google Domains (@ A 1H 93.49.98.183) and tried a free subdomain at duckdns but I get the same issue so I suspect troubles are in my host\caddy. now the Caddyfile is:
Is Caddy running directly on the Proxmox host or in a guest VM / container?
The more I think about it, the more I reckon 443 is being intercepted and sent somewhere other than Caddy. I note that you have not once yet in this thread had success over port 443 regardless of what certificates or Caddy configuration you use.
My modem\router is just crap. Turns out port forwarding sometimes doesn’t work correctly, after further investigating the issue as you suggested it was a networking issue. Tried with other hardware and everything worked like plug-n-play.