Failed authorization procedure

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:
nextcloud.regener8.cf

I ran this command:
certbot
It produced this output:
certbot
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator apache, Installer apache
Starting new HTTPS connection (1): acme-v02.api.letsencrypt.org

Which names would you like to activate HTTPS for?


1: nextcloud.regener8.tk
2: nextcloud.regener8.cf
3: nextcloud.regener8portadown.net
4: www.regener8portadown.net


Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter ‘c’ to cancel): 2
Cert is due for renewal, auto-renewing…
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for nextcloud.regener8.cf
Waiting for verification…
Cleaning up challenges
Failed authorization procedure. nextcloud.regener8.cf (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://nextcloud.regener8.cf/.well-known/acme-challenge/_nURJaXnlGUvMx6b3MeyyhbmWbwvzULPV7t5SXM3qY4: Timeout during connect (likely firewall problem)

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: nextcloud.regener8.cf
    Type: connection
    Detail: Fetching
    http://nextcloud.regener8.cf/.well-known/acme-challenge/_nURJaXnlGUvMx6b3MeyyhbmWbwvzULPV7t5SXM3qY4:
    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):

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

My hosting provider, if applicable, is:

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

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

certbot 0.31.0

Confirmed:
curl -Iki http://nextcloud.regener8.cf/
curl: (7) Failed to connect to nextcloud.regener8.cf port 80: Connection timed out

Port 80 is required to be open for HTTP validations.

Hi @dieselfreak

there are a lot of older certificates.

Issuer not before not after Domain names LE-Duplicate next LE
Let’s Encrypt Authority X3 2019-10-17 2020-01-15 nextcloud.regener8.cf
1 entries
Let’s Encrypt Authority X3 2019-07-15 2019-10-13 nextcloud.regener8.cf
1 entries
Let’s Encrypt Authority X3 2019-04-29 2019-07-28 nextcloud.regener8.cf
1 entries
Let’s Encrypt Authority X3 2019-01-20 2019-04-20 nextcloud.regener8.cf
1 entries

Your old topic

There you have used webroot. An open port 80 is required to create a certificate, not a timeout.

thanks… new router… forgot to add http rule.

2 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.