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:landwtools.com
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don’t know):
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):
it returns the following error :
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for landwtools.com
http-01 challenge for www.landwtools.com
Using the webroot path /var/lib/letsencrypt for all unmatched domains.
Waiting for verification…
Cleaning up challenges
Failed authorization procedure. www.landwtools.com (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://www.landwtools.com/… [188.8.131.52]: “\r\n404 Not Found\r\n<body bgcolor=”“white”">\r\n
404 Not Found\r\n
", landwtools.com (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://landwtools.com/.well… [184.108.40.206]: “\r\n404 Not Found\r\n<body bgcolor=”“white”">\r\n
404 Not Found\r\n
- The following errors were reported by the server:
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.
previously, I am okay for the let’s encrypt process with my old elastic IP, and now, when I upgrade my aws ec2 instance, I incorrectly delete my previously associated elastic IP address, so I have to choose a new elastic IP, and then when I re-process the Let’s Encrypt, those error are happened.
Any suugestion for the fix? Thanks in advance