My server is down!

[acortes]

SYSTEM INFORMATION
OS type and version	Rocky Linux 8.6
—	—
Webmin version	2.201
Virtualmin version	7.20.2

SOS! My virtual servers suddenly stopped. I can’t access any of them, for example https://demo.oclockdt.com.
I rebooted. but it’s still the same.
It all started when on one of them the SSL stopped working without warning., I did:
sudo certbot certonly -d ce.oclockdt.com
and everything stopped working. Can you help me? Thanks, The whole system is down!

[acortes]

[root@ns3226653 ~]# sudo systemctl status httpd
● httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
Drop-In: /usr/lib/systemd/system/httpd.service.d
└─php-fpm.conf
/etc/systemd/system/httpd.service.d
└─php80-php-fpm.conf, php81-php-fpm.conf
Active: failed (Result: exit-code) since Wed 2024-09-11 21:45:01 CEST; 4min 40s ago
Docs: man:httpd.service(8)
Process: 11273 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
Main PID: 11273 (code=exited, status=1/FAILURE)
Status: “Reading configuration…”

Sep 11 21:45:01 ns3226653.ip-162-19-89.eu systemd[1]: Starting The Apache HTTP Server…
Sep 11 21:45:01 ns3226653.ip-162-19-89.eu httpd[11273]: AH00112: Warning: DocumentRoot [/home/winforme/public_html] doe>
Sep 11 21:45:01 ns3226653.ip-162-19-89.eu httpd[11273]: AH00526: Syntax error on line 920 of /etc/httpd/conf/httpd.conf:
Sep 11 21:45:01 ns3226653.ip-162-19-89.eu httpd[11273]: SSLCertificateFile: file '/etc/ssl/virtualmin/172304409677701/s>
Sep 11 21:45:01 ns3226653.ip-162-19-89.eu systemd[1]: httpd.service: Main process exited, code=exited, status=1/FAILURE
Sep 11 21:45:01 ns3226653.ip-162-19-89.eu systemd[1]: httpd.service: Failed with result ‘exit-code’.
Sep 11 21:45:01 ns3226653.ip-162-19-89.eu systemd[1]: Failed to start The Apache HTTP Server.

[acortes]

Fixed, it was an error in an httpd.conf directive.

[Joe]

Glad you got it sorted.

I just want to mention, you should only use certbot directly if Virtualmin is not managing your Let’s Encrypt certificates. (It’s fine, either way, but, there are differences in how things work and where files end up, and if you try to use both, you’ll confuse yourself and both tools.)