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.
I ran this command:sudo certbot certonly --standalone --preferred-challenges http -d sbsartis.b2m-it.com
It produced this output: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 sbsartis.b2m-it.com
Cleaning up challenges
Problem binding to port 80: Could not bind to IPv4 or IPv6.
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):
sbsartis.b2m-it.com has an A (IPv4) record (220.127.116.11) but a request to this address over port 80 did not succeed. Your web server must have at least one working IPv4 or IPv6 address.
A timeout was experienced while communicating with sbsartis.b2m-it.com/18.104.22.168: Get "http://sbsartis.b2m-it.com/.well-known/acme-challenge/letsdebug-test": dial tcp 22.214.171.124:80: i/o timeout
@0ms: Making a request to http://sbsartis.b2m-it.com/.well-known/acme-challenge/letsdebug-test (using initial IP 126.96.36.199)
@0ms: Dialing 188.8.131.52
@10000ms: Experienced error: dial tcp 184.108.40.206:80: i/o timeout
A test authorization for sbsartis.b2m-it.com to the Let's Encrypt staging service has revealed issues that may prevent any certificate for this domain being issued.
220.127.116.11: Fetching http://sbsartis.b2m-it.com/.well-known/acme-challenge/34CQz6nWYCROLfR1BzNYKCUgKqAhray-BYdZCnEBItk: Timeout during connect (likely firewall problem)
Also, it seems your thread title does not correspond with the thread contents, as clearly different errors are presented. How does the policy error relate to the hostname you've mentioned in the thread?
And nmap -Pn sbsartis.b2m-it.com seems to confirm this.
$ nmap -Pn sbsartis.b2m-it.com
Starting Nmap 7.80 ( https://nmap.org ) at 2023-04-26 16:34 UTC
Nmap scan report for sbsartis.b2m-it.com (18.104.22.168)
Host is up.
All 1000 scanned ports on sbsartis.b2m-it.com (22.214.171.124) are filtered
Nmap done: 1 IP address (1 host up) scanned in 202.17 seconds
Apart from the port issue mentioned above, I guess you simply copied the command from user guide and included example.com literally as domain name without any modification, as indicated by the error message in the subject.