I had certbot renew scheduled to run. It ran fine for a few months, even renewed the certificates twice. Last night it ran successfully, and the certificates were generated, but the website does not load.
When I load the backup image, I can see one root httpd server and 4 user processes. This is the command I use: sudo lsof -i tcp:80 -s tcp:listen
On the latest updated version, it shows one root and 3 user httpd processes.
Environment: Centos 7
The certbot is 0.27.1
The systemctl status shows httpd is Active. But the website does not load.
regular systemctl stop/start httpd do not do any good.
Logs do not show any errors (checked /var/log/letsencrypt).
My certificate expired a few hours back.
I would like at least to properly restart the httpd service, so I can have the next 90 days putting in a proper fix. Please help.
please answer the following questions. That’s the standard template of #help
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):
The operating system my web server runs on is (include version):
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):
No secrets from you. Just did not know how much info is required. Thank you for guiding me.
The domain is: back2rent.com
The web server is: apache 2.4.29
Operation System: Centos 7
Provider: Linode
I use command line. Have full admin.
I do not use any control panel (besides Linode DNS Manager)
The certbot version is 0.27.1
The command that caused the issue is certbot renew --apache
Now that I think of it, during the last “not up for renewal” run, apache also went down. I just went back to prior backup image without doing any investigation.
– I did some troubleshooting yesterday. --dry-run option also brings the server down.
ConnectFailure - Unable to connect to the remote server No connection could be made because the target machine actively refused it [2600:3c02::f03c:91ff:fecc:210a]:443
ConnectFailure - Unable to connect to the remote server No connection could be made because the target machine actively refused it [2600:3c02::f03c:91ff:fecc:210a]:443
Sorry for silly questions. I am not sysadmin by trade, used google and forums to install everything.
I already have a certificate generated by letsencrypt last night. I validated it with openssl command, and it showed that it is valid and expires in June. I thought I could use it, and the only issue is https connection.
Both of these websites ran together on the same box and their certificates were issued and renewed with the same process.
Yesterday I moved floridamakler.com to a different box. Both boxes are built from the same backup image. So, before the “certbot renew” runs, both servers are identical. The certificate expired today in the morning, so I do not know if querying the floridamakler.com will provide any clues.
I compared both, apache and letsencrypt folders on both nodes, and they are identical even after the certbot run. With exception of a newly created certificate.
The initial httpd-ssl.conf was initially created by the certbot when I first created the certifcates back in November. I also had issues with redirecting 80 to 443, so I disconnected the redirect.
Something happens after the certbot runs. The only thing that I saw promising is the number of apache instances. Before the run I run the command to see what is listening on port 80. The result is 1 process run as root and 4 processes run as apache (user). After the run I see 1 as root and 3 as user. I reloaded the image multiple times and always the same thing.
I fixed the problem. But still do not know the root cause.
The certificates were generated successfully, so I copied them to the other server to the /etc/letsencrypt/archive, modified links in the /etc/letsencrypt/live/back2rent.com to point to the new certificates. And rebooted the server (probably restart httpd would have also worked).