Certbot renew fails

Help
1

Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator standalone, Installer None
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for jarfx.dyndns.org
Waiting for verification…
Challenge failed for domain jarfx.dyndns.org
http-01 challenge for jarfx.dyndns.org
Cleaning up challenges
Attempting to renew cert (jarfx.dyndns.org) from /etc/letsencrypt/renewal/jarfx.dyndns.org.conf produced an unexpected error: Some challenges have failed… Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/jarfx.dyndns.org/fullchain.pem (failure)

://jarfx.dyndns.org/.well-known/acme-challenge/LpKiFIpzycSdXMy3THHKU_0QJ-bCqzufSPy8gyTbP8U:
Timeout during connect (likely firewall problem)
My firewalls are open.
I had to turn apache2 off or I got a cannot bind to port 80 message.
My domain is: jarfx.dyndns.org

I ran this command: certbot certonly --standalone

It produced this output: the certificates were made

My web server is (include version): Apache2, but want to use cert on Openfire and subsonic

The operating system my web server runs on is (include version): OpenSUSE Leap 15.1

My hosting provider, if applicable, is:
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):

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

What is the pass phrase for the private key made by certbot? this is private

2

Hi @jimrome

checking your domain there is no running webserver - https://check-your-website.server-daten.de/?q=jarfx.dyndns.org

Do you have a webserver? --standalone starts an own, so it's hard to debug.

Your last certificate is old:

Issuer not before not after Domain names LE-Duplicate next LE
Let's Encrypt Authority X3 2019-07-16 2019-10-14 jarfx.dyndns.org
1 entries

So the easiest solution:

Start an own webserver. Then test, if your domain is visible. Then use --apache or --webroot to create a certificate.

3

I had to turn Apache off, Otherwise I got a “could not bind to port 80” message. But I started Apache and tried again. I still get a timeout:

ertbot --apache
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator apache, Installer apache
No names were found in your configuration files. Please enter in your domain
name(s) (comma and/or space separated) (Enter ‘c’ to cancel): jarfx.dyndns.org
Cert is due for renewal, auto-renewing…
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for jarfx.dyndns.org
Waiting for verification…
Challenge failed for domain jarfx.dyndns.org
http-01 challenge for jarfx.dyndns.org
Cleaning up challenges
Some challenges have failed.

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: jarfx.dyndns.org
    Type: connection
    Detail: Fetching
    http://jarfx.dyndns.org/.well-known/acme-challenge/qQN6kfl4rqm-47BoZ8GjmeX7cDqT4yMvfYQZtlxf8jI:
    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.

4

Hi,

Your domain has a timeout on port 80, so could you please double check on port-forwarding? Did you start your firewall?

https://letsdebug.net/jarfx.dyndns.org/64225

Thank you

5

Thanks for the help. I had turned Apache2 off because certbot said it could not bind to that port. However, it still was not answering requests until I turned on the firewall on my Linux machine (SUSE Leap 15.1). Really strange. Now it renewed the cert.

6

That happens if you use --standalone.

But if you don't have a running webserver, it's impossible to check if it is a router forward problem, a closed firewall or another problem.

Running webserver -> test of the firewall + router is possible.

7

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