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. crt.sh | 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: ftp.sharezone.it and mail.sharezone.it
I ran this command:
certbot certonly --standalone --preferred-challenges http -d mail.sharezone.it
certbot certonly --standalone --preferred-challenges http -d ftp.sharezone.it
It produced this output:
for the firset command the certificate generate without issue
for the second command i recevie
root@armcrt01:/etc/letsencrypt# certbot certonly --standalone --preferred-challenges http -d mail.sharezone.cloud
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator standalone, Installer None
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for mail.sharezone.cloud
Waiting for verification...
Cleaning up challenges
Failed authorization procedure. mail.sharezone.cloud (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from https://mail.sharezone.cloud/.well-known/acme-challenge/Vgt9HlJB-nzHBpkruGysRX05ZsDmp_A1per8pZlOYNw [18.104.22.168]: "\n\n<html lang="en">\n \n <meta charset="utf-8" />\n \n <link rel="icon" type="image/png"
The following errors were reported by the server:
Domain: mail.sharezone.cloud\n \n <link rel=\"icon\" type=\"image/png"
Detail: Invalid response from
[22.214.171.124]: "\n\n<html lang="en">\n \n
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.
The operating system my web server runs on is (include version): debian 10
My hosting provider, if applicable, is: locally hosting
I can login to a root shell on my machine (yes or no, or I don't know): yes i have full access
The version of my client is (e.g. output of
certbot --version or
certbot-auto --version if you're using Certbot):
root@armcrt01:/etc/letsencrypt# certbot --version