Hi, I’m trying to get a certificate for app.instapack.es. The real domain is instapack.es that already has a certificate but is pointing to another host, my current nginx configuration for the subdomain is:
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address.
Visible Content: Oops! An Error Occurred The server returned a "404 Not Found". Something is broken. Please let us know what you were doing when this error occurred. We will fix it as soon as possible. Sorry for any inconvenience caused.
Visible Content: Oops! An Error Occurred The server returned a "404 Not Found". Something is broken. Please let us know what you were doing when this error occurred. We will fix it as soon as possible. Sorry for any inconvenience caused.
Checking /.well-known/acme-challenge/random-filename ipv4 answers with the expected result 404 - Not Found. Ipv6 has a http status 204.
Result:
Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>.
thanks @JuergenAuer crack I have removed the IPv6 address from my DNS because currently my application hosted in azure has only the ipv4 address configured. Thanks again