I’ve always had issues with LetsEncrypt moving SSL’s about - whenever I’d generate a new certificate, it’d also apply the new certificate to the site I’d previously set up. So I’d need to go back and re-install the certicate for it to work.
I’ve moved over a domain, and it quickly picked up the certificate for another one of my sites. I believe this is causing the issue as I’ve never had this problem before. I tried removing the cert it was picking up - but it just went and took the next site in the list’s cert.
Why is https not just 404ing? Is there some catch-all that’s messing with me ?
Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is: golfjobslist.co.uk/
I ran this command: sudo /usr/local/bin/certbot-auto --nginx
It produced this output:
Performing the following challenges:
http-01 challenge for golfjobslist.co.uk
Waiting for verification…
Challenge failed for domain golfjobslist.co.uk
http-01 challenge for golfjobslist.co.uk
Cleaning up challenges
Some challenges have failed.
IMPORTANT NOTES:
-
The following errors were reported by the server:
Domain: golfjobslist.co.uk
Type: unauthorized
Detail: Invalid response from
http://golfjobslist.co.uk/.well-known/acme-challenge/Nu64S51uL9ToAaapjV1YGBAfTObAgsHbLH0-kyZ74f8
[2a01:7e00::f03c:92ff:fe37:c20b]: “\r\n404 Not
Found\r\n<body bgcolor=“white”>\r\n404
\r\n
Not Found
”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.
My web server is (include version): nginx/1.14.1
The operating system my web server runs on is (include version): CentOS 8
My hosting provider, if applicable, is: Linode
I can login to a root shell on my machine (yes or no, or I don’t know): yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): no
The version of my client is (e.g. output of certbot --version
or certbot-auto --version
if you’re using Certbot): certbot 1.1.0
my nginx.conf looks like this current
# golfjobslist.co.uk
server {
listen 80;
server_name golfjobslist.co.uk;
return 301 http://www.golfjobslist.co.uk$request_uri;
}
server {
listen 80;
server_name www.golfjobslist.co.uk;
root /usr/share/nginx/html/golfjobs;
}