Turned out was either an iptables rule, or that I had an AAAA record for the subdomain, but ipv6 disabled on the server.
I'll leave the original question for anyone that may find themselves in a similar position.
-------------
Anyone else having problems updating?
Nginx logs show a 301 and then a 404 after failure.
Output of letsncrypt script says possible firewall issue.
Login panel opens fine from everywhere online.
Helps? Does letsncrypt still block on multiple failures as I'm worried to keep trying.
Just a single subdomain and this is an update to an existing cert that has been working fine.
I usually modify the ipv4 rules to tighten things down but I've opened up 80 and 443 to be world accessible.
A local wget of the challenge also returns 404.
Thanks in advance
I'll leave the original question for anyone that may find themselves in a similar position.
-------------
Anyone else having problems updating?
Nginx logs show a 301 and then a 404 after failure.
Output of letsncrypt script says possible firewall issue.
Login panel opens fine from everywhere online.
Helps? Does letsncrypt still block on multiple failures as I'm worried to keep trying.
Just a single subdomain and this is an update to an existing cert that has been working fine.
I usually modify the ipv4 rules to tighten things down but I've opened up 80 and 443 to be world accessible.
A local wget of the challenge also returns 404.
Thanks in advance
Last edited: