My name is Richard Watson and I'm a professional PHP developer
from Lurgan in Northern Ireland
Posted by richard
Other | 10-10-2018
You're messing with Apache and now it won't start. What's next?
Today, I managed to break a web server. Badly? No. Rolling out some tests on a self-signed certificate and Apache wouldn't start. I'd rolled back all my changes, so what could possibly have went wrong?
The server.crt certificate.
This isn't a big problem, you can create a self-signed cert from makecert.bat in the Xampp/Apache directory at any time, but the apache error log wasn't giving me any information. When that happens, what should you do? The answer is the Windows Event Viewer which you can launch by going to start > run > eventvwr.msc.
It's also not the first time (Or thousandth time) I've had to diagnose a simple problem this way, but frustrating none the less that the Apache error log didn't tell me I'd been a fool and removed the original server.crt file, which it needs for HTTP/HTTPS dual mode even if you're not using HTTPS. A little tip worth remembering next time you can't seem to diagnose a faulty Apache service - whether you broke it yourself or not.
Frameworks & tools