Xampp Control Panel having two sets of configs is a bad idea
Posted: 12. January 2015 07:50
Xampp Control Panel having two sets of configs is a bad idea. At least they should work together.
I changed the port numbers for Apache in the httpd.conf & hhtps-ssl.conf files (known this years ago) and Apache couldn't start and error showed it tried to use 80 and 443. What?
Is it not reading those config files? Then I noticed the other Config button and the 'Service and Port Settings' and they had their own port numbers settings. Changed them. Apache still couldn't start but it didn't mention port 80 and 443 anymore. Just it stopped unexpectedly. Log files are empty. Windows event log has nothing about Apache. What the hell is going on?
After some mocking I found out the port numbers needed to match in the different config settings.
Sheesh. Why doesn't XAMPP's config setting change the other setting files as well? Also the error message should indicate clearly the port settings mismatch. Annoying.
I changed the port numbers for Apache in the httpd.conf & hhtps-ssl.conf files (known this years ago) and Apache couldn't start and error showed it tried to use 80 and 443. What?
Is it not reading those config files? Then I noticed the other Config button and the 'Service and Port Settings' and they had their own port numbers settings. Changed them. Apache still couldn't start but it didn't mention port 80 and 443 anymore. Just it stopped unexpectedly. Log files are empty. Windows event log has nothing about Apache. What the hell is going on?
After some mocking I found out the port numbers needed to match in the different config settings.
Sheesh. Why doesn't XAMPP's config setting change the other setting files as well? Also the error message should indicate clearly the port settings mismatch. Annoying.