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: plantnation.co.za
I ran this command: certbot --nginx
It produced this output:
Failed authorization procedure. www.plantnation.co.za (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://www.plantnation.co.za/.well-known/acme-challenge/np4qCfQwgUHwnB2WB-WQp6XXRxx9JW7twqRtGi8deTk [197.242.144.234]: “\n\n404 Not Found\n\n
Not Found
\n<p”IMPORTANT NOTES:
-
The following errors were reported by the server:
Domain: www.plantnation.co.za
Type: unauthorized
Detail: Invalid response from
http://www.plantnation.co.za/.well-known/acme-challenge/np4qCfQwgUHwnB2WB-WQp6XXRxx9JW7twqRtGi8deTk
[197.242.144.234]: “\n\n404 Not
Found\n\nNot Found
\n<p”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.10.3
The operating system my web server runs on is (include version): ubuntu 16.04
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):
The version of my client is (e.g. output of certbot --version
or certbot-auto --version
if you’re using Certbot): certbot 0.31.0
I pointed two domains by means of changing the A records to my new server, plantlifesa.co.za and plantnation.co.za, after propagation I ran certbot for plantlifesa.co.za and it went through smoothly. When trying with plantnation.co.za I get the failed process. In the failed process where it shows the IP address, it for some reason shows the old server IP address. I have tried many times over many days since propagation and its still the same issue.
Im not sure why the authorization procedure is getting the wrong ip address?
Please assist.
Thanks,
Tay