Cannot create certificate

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:
influxdb-prod.allthingssmart.be

I ran this command:
$ sudo certbot certonly --standalone

It produced this output:
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for influxdb-prod.allthingssmart.be
Waiting for verification…
Cleaning up challenges
Failed authorization procedure. influxdb-prod.allthingssmart.be (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://influxdb-prod.allthingssmart.be/.well-known/acme-challenge/PDvSPxbhLVO4vVHXlQxvdw2hfAcTR-IgE5tIjd6W2KA: Timeout during connect (likely firewall problem)

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: influxdb-prod.allthingssmart.be
    Type: connection
    Detail: Fetching
    http://influxdb-prod.allthingssmart.be/.well-known/acme-challenge/PDvSPxbhLVO4vVHXlQxvdw2hfAcTR-IgE5tIjd6W2KA:
    Timeout during connect (likely firewall problem)

    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. Additionally, please check that
    your computer has a publicly routable IP address and that no
    firewalls are preventing the server from communicating with the
    client. If you’re using the webroot plugin, you should also verify
    that you are serving files from the webroot path you provided.

  • Your account credentials have been saved in your Certbot
    configuration directory at /etc/letsencrypt. You should make a
    secure backup of this folder now. This configuration directory will
    also contain certificates and private keys obtained by Certbot so
    making regular backups of this folder is ideal.

  • We were unable to subscribe you the EFF mailing list because your
    e-mail address appears to be invalid. You can try again later by
    visiting https://act.eff.org.
    vmadmin@itp-az-usea-prod-influxdb-vm1:~$ sudo certbot certonly --standalone --staging
    Saving debug log to /var/log/letsencrypt/letsencrypt.log
    Plugins selected: Authenticator standalone, Installer None
    Please enter in your domain name(s) (comma and/or space separated) (Enter ‘c’
    to cancel): influxdb-prod.allthingssmart.be
    Obtaining a new certificate
    Performing the following challenges:
    http-01 challenge for influxdb-prod.allthingssmart.be
    Waiting for verification…
    Cleaning up challenges
    Failed authorization procedure. influxdb-prod.allthingssmart.be (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://influxdb-prod.allthingssmart.be/.well-known/acme-challenge/bF_amSLccJh2CPKI23AydR7tnCtGICorpA6p1T2N7-0: Timeout during connect (likely firewall problem)

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: influxdb-prod.allthingssmart.be
    Type: connection
    Detail: Fetching
    http://influxdb-prod.allthingssmart.be/.well-known/acme-challenge/bF_amSLccJh2CPKI23AydR7tnCtGICorpA6p1T2N7-0:
    Timeout during connect (likely firewall problem)

    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. Additionally, please check that
    your computer has a publicly routable IP address and that no
    firewalls are preventing the server from communicating with the
    client. If you’re using the webroot plugin, you should also verify
    that you are serving files from the webroot path you provided.

My web server is (include version):
N/A

The operating system my web server runs on is (include version):
Ubuntu 18.04

My hosting provider, if applicable, is:
Azure

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):
yes

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):
0.31.0

1 Like

Hi @gdillen,

I agree with the Let’s Encrypt server’s speculation here: it looks like you have a firewall somewhere (either on your own server instance, or at your hoster level) that is preventing inbound connections from the Internet on port 80. Allowing these connections is required in order to get a certificate by this method.

2 Likes

Thanks.
Indeed, the mistake I made was in in the Inbound rule -> Source Port Ranges I mistakenly had put 80 instead of *.

1 Like