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. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
I ran this command to get the certificate(s):
(I can't remember exactly but I think it was:
sudo certbot --apache -d www.cworklog.com --post-hook "/usr/sbin/service apache2 restart"
It produced this output:
I am afraid to run it again lest i mess something up.
My web server is (include version):
13:28 /home/deploy $ /usr/sbin/apache2 -v
Server version: Apache/2.4.38 (Debian)
Server built: 2020-08-25T20:08:29
My hosting provider, if applicable, is:
Linode
I can login to a root shell on my machine (yes or no, or I don't know):
Yes I have root access to the shell.
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
no, just root access
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
Glad you got your certificate working! What JuergenAuer is recommending is what's known as a "canonical name", which ensures singular URL addressing for your website and helps with SEO.
Since you're using both the apache authenticator and installer, the installer will reload apache for you when the authenticator successfully acquires/renews your certificate. Therefore you don't need to restart it with a hook. Moreover, the post hook will run EVERY time a renewal attempt is made, even if your certificate is not actually renewed (due to not being close to expiry). The deploy hook is more appropriate, but still not necessary here.
You would also want to gracefully reload apache to prevent downtime rather than doing a hard restart: