Site unreachable after certbot

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: test.designing-history.world

I ran this command: certbot --apache

It produced this output:
sudo certbot --apache
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator apache, Installer apache

Which names would you like to activate HTTPS for?


1: nctest.designing-history.world
2: www.nctest.designing-history.world
3: test.designing-history.world


Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter ‘c’ to cancel):


You have an existing certificate that contains a portion of the domains you
requested (ref: /etc/letsencrypt/renewal/test.designing-history.world.conf)

It contains these names: test.designing-history.world

You requested these names for the new certificate:
nctest.designing-history.world, www.nctest.designing-history.world,
test.designing-history.world.

Do you want to expand and replace this existing certificate with the new
certificate?


(E)xpand/©ancel: e
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for test.designing-history.world
http-01 challenge for nctest.designing-history.world
http-01 challenge for www.nctest.designing-history.world
Waiting for verification…
Cleaning up challenges
Failed authorization procedure. www.nctest.designing-history.world (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://www.nctest.designing-history.world/.well-known/acme-challenge/V6aAZsEBy-jSwF4MuCO3oWp7Scw-2rlTc6FADPUoVFY [2a01:488:66:1000:57e6:e14:0:1]: “\n\n404 Not Found\n\n

Not Found

\n<p”

IMPORTANT NOTES:

My web server is (include version): apache2

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

My hosting provider, if applicable, is: hosteurope.com

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

1 Like

Hi @der_spotter

checking the first domain that looks wrong - https://check-your-website.server-daten.de/?q=nctest.designing-history.world

Host T IP-Address is auth. ∑ Queries ∑ Timeout
nctest.designing-history.world A 92.51.167.157 Hürth/North Rhine-Westphalia/Germany (DE) - HE-LVPS Hostname: lvps92-51-167-157.dedicated.hosteurope.de yes 1 0
AAAA yes
www.nctest.designing-history.world A 87.230.14.20 Hürth/North Rhine-Westphalia/Germany (DE) - Host Europe GmbH Hostname: designing-history.world yes 1 0
AAAA 2a01:488:66:1000:57e6:e14:0:1 Cologne/North Rhine-Westphalia/Germany (DE) - HER INITIAL yes

Is 92.51… the same server like 87.230… and the ipv6?

If not, normally, that can’t work.

Didn’t checked your third domain. All should have the same ip addresses.

1 Like

no, they are different servers. however this doesnt explain why i can read the server without problems and after certbot the connection just times out.
i needed about 3 hours to fix it after running certbot, then ran certbot again and now i have the same problem

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