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:
I ran this command:
It produced this output:
My web server is (include version): apache2.4
The operating system my web server runs on is (include version): Ubuntu 18.04.3 LTS
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don’t know):
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.31.0
Certbot renewal is not a problem for me. The certs get renewed successfully. However the post hook which is supposed to start apache2 back up again does not seem to bring up the server. Where would i look for any logs to see what is going on? The apache error.log does not report anything and neither does the syslog around that same time.
Here is the end of the letsencrypt.log:
2019-10-31 22:21:18,646:DEBUG:certbot.plugins.selection:Requested authenticator standalone and installer apache
2019-10-31 22:21:18,648:DEBUG:certbot.plugins.selection:Selecting plugin: * apache
Description: Apache Web Server plugin
Interfaces: IAuthenticator, IInstaller, IPlugin
Entry point: apache = certbot_apache.entrypoint:ENTRYPOINT
Initialized: <certbot_apache.override_debian.DebianConfigurator object at 0x7f1a37a9c9b0>
Prep: True
2019-10-31 22:21:18,648:DEBUG:certbot.renewal:no renewal failures
2019-10-31 22:21:18,648:INFO:certbot.hooks:Running post-hook command: service apache2 start