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: socketclient.com
I ran this command: sudo certbot renew --dry-run
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Processing /etc/letsencrypt/renewal/socketclient.com.conf
Cert not due for renewal, but simulating renewal for dry run
Plugins selected: Authenticator webroot, Installer None
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for socketclient.com
http-01 challenge for www.socketclient.com
Waiting for verificationâŚ
Cleaning up challenges
Attempting to renew cert (socketclient.com) from /etc/letsencrypt/renewal/socketclient.com.conf produced an unexpected error: Failed authorization procedure. www.socketclient.com (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from https://www.socketclient.com/.well-known/acme-challenge/51kmC_caQDA6Wu9UarD7s4dKpknbpMvAo8_ZzLE-kgQ [167.114.2.125]: 404, socketclient.com (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from https://socketclient.com/.well-known/acme-challenge/m77H-AM8w8KuXIYJHEif682UZjtPkEBrNqf9t6yNc2U [167.114.2.125]: 404. Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/socketclient.com/fullchain.pem (failure)
** DRY RUN: simulating âcertbot renewâ close to cert expiry
** (The test certificates below have not been saved.)
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/socketclient.com/fullchain.pem (failure)
** DRY RUN: simulating âcertbot renewâ close to cert expiry
** (The test certificates above have not been saved.)
1 renew failure(s), 0 parse failure(s)
IMPORTANT NOTES:
-
The following errors were reported by the server:
Domain: www.socketclient.com
Type: unauthorized
Detail: Invalid response from
https://www.socketclient.com/.well-known/acme-challenge/51kmC_caQDA6Wu9UarD7s4dKpknbpMvAo8_ZzLE-kgQ
[167.114.2.125]: 404Domain: socketclient.com
Type: unauthorized
Detail: Invalid response from
https://socketclient.com/.well-known/acme-challenge/m77H-AM8w8KuXIYJHEif682UZjtPkEBrNqf9t6yNc2U
[167.114.2.125]: 404To 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): Golang(Echo framework)
The operating system my web server runs on is (include version): Debian 9
My hosting provider, if applicable, is: Namecheap
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): webmin-latest
The version of my client is (e.g. output of certbot --version
or certbot-auto --version
if youâre using Certbot): 0.28
Additionally i can reach : https://socketclient.com/.well-known/acme-challenge/name.txt
Once i created a standalone cert, it created webroot succesfully.
I have 2 other servers i need to renew but same setup as this and same errors.