Hi,
I know I didn't create a new productive certificate, that's why I mentioned that I did “break-my-certs” to use fake certs at my webserver.
The renewal with the fake certificates was succesfull - but like before my apache crashed! I found a case of someone who had the same problem: Certbot renew segfaults my apache2 - wrote him a message and I hope he has some solution.
And that is where the really strange things happen:
root@Junkrat:~# certbot renew --force-renewal --preferred-challenge http-01 --server https://acme-v02.api.letsencrypt.org/directory
Saving debug log to /var/log/letsencrypt/letsencrypt.log
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Processing /etc/letsencrypt/renewal/gnaarl.de.conf
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Plugins selected: Authenticator apache, Installer apache
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for gnaarl.de
http-01 challenge for mail.gnaarl.de
http-01 challenge for www.gnaarl.de
Waiting for verification...
Cleaning up challenges
Attempting to renew cert (gnaarl.de) from /etc/letsencrypt/renewal/gnaarl.de.conf produced an unexpected error: Failed authorization procedure. gnaarl.de (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://gnaarl.de/.well-known/acme-challenge/NpybEtOhNou-mVIpTwZDUCIsH9MtO70MG5vi-J94jr0: Timeout after connect (your server may be slow or overloaded), www.gnaarl.de (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://www.gnaarl.de/.well-known/acme-challenge/JH9S-gZF8vQh4VrZkVLpSilFP3_nJEVWAXnL9yz1lwY: Timeout after connect (your server may be slow or overloaded), mail.gnaarl.de (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://mail.gnaarl.de/.well-known/acme-challenge/1FktXdlu09nB_RxmCeAx706ZuG7H8NYlBZz274DVB1w: Timeout after connect (your server may be slow or overloaded). Skipping.
The same error as before. I don't get why the same config is renewing my Test-Cert (even if the apache crashes) but can not renew my productive cert (I think because the apache crashes).
Since "apache2ctl graceful" leads to an apache crash - is there a way to let certbot do a full restart instead of a graceful restart?!?
edit: Even an "apache2ctl restart" is causing the segmentation faults and a crash... Only /etc/init.d/apache2 restart seems to do the job...