Can't renew certificate since TLS-SNI-01 end-of-life

Help
3

Thanks for your great hint to on the update! Learning on dnf features :slight_smile:
The update mainly worked, except something minor which I would consider not important for updating certbot.

Details here on fedora update problem

I executed

sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2019-2361aca4af

and it work for the most part, except for some error which I would consider not important for updating certbot.
Fehlgeschlagen:
python2-configobj-5.0.6-14.fc29.noarch

Fehler: Transaktion fehlgeschlagen

Unfortunately now the second underlaying problem shows up when trying to update the certificate:

Status now is:

$ certbot --version
certbot 0.34.2

I ran this command:

certbot --apache renew

It produced this output:

Saving debug log to /var/log/letsencrypt/letsencrypt.log

Processing /etc/letsencrypt/renewal/maier.dyn.cc.conf

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

All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/maier.dyn.cc/fullchain.pem (failure)

1 renew failure(s), 0 parse failure(s)

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: maier.dyn.cc
    Type: connection
    Detail: Fetching
    http://maier.dyn.cc/.well-known/acme-challenge/sssLDP-aCoX-NiKSFM9XIMG_Sqrf8A3xu8-lUTJ5GKM:
    Error getting validation data

    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.

Any hint on what to do / check next would be great.