AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
If you still have trouble starting Apache after trying the solutions above, then your issue is very specific to your machine. The folder that contains xampp-control.exe is where XAMPP was installed.Īrticle continues after the advertisement: 3. If you can’t find where XAMPP is installed on your computer, you can also do a search for xampp-control.exe on your File Explorer. Always uninstall through Add or remove programs (or the Control Panel) if you have the option. Otherwise, if you can’t find XAMPP on Add or remove programs, you will have to find the folder where XAMPP is and manually remove the folder (it is usually found in C:\xampp). If you can uninstall it through the Add or remove programs interface, that would be best. In most cases, re-installation will be the easier option. Re-install XAMPP (here’s the official source).Read the log files to find out what happened, or.If neither of the 2 fixes above worked for you, then there is likely a misconfiguration in your XAMPP installation or Apache config files. Try to start the XAMPP Apache web server again.Now, you are able to turn on/off W3PS manually. In the General tab, click Startup Type and switch it to manual.The World Wide Web Publishing Service (W3PS) on the Service Manager. To deactivate the W3PS service (so that it doesn’t automatically start on your Windows device): The W3PS is a component of Windows’ Internet Information Services (IIS) - which is responsible for providing HTTP and HTTPS services on Windows machines - may be using port 80, thereby not allowing XAMPP Apache to connect to the same port.īelow, you can read instructions on how to either deactivate or stop the W3PS service, so that port 80 can be freed up for Apache’s use. If you are running a Windows server machine, you may have a process running called the World Wide Web Publishing Service (W3PS). Disabling the World Wide Web Publishing Service (W3PS) In this case, you will want to undo the changes made to nf, so that Apache is back to using Port 80. If XAMPP still fails to start after changing your port, that means that the problem is not caused by a blocked port. Note that for pre-existing virtual hosts on your XAMPP Apache, you will also need to update them to listen to port 8080 instead of 80. For example, if Apache listens to port 8080, the URL you will have to access will be localhost:8080 instead of the default localhost. Note that if you are using any other port than 80 or 443, you will have to append the port number at the end of the URL to access the page(s) on XAMPP. Where the Config button is in the XAMPP Control Panel.Īrticle continues after the advertisement: If the problem was due to a blocked port, Apache should now start with no problem. Once done, try starting Apache on XAMPP again.In the file, search for Listen 80 and change it to Listen 8080.Click on the Config button next to the Apache Web server (refer to the image below), and select nf.To change XAMPP Apache’s port number, refer to the steps below: To determine if port 80 being blocked is your actual problem, you can change the default port number for Apache and see if it fixes your issue. To fix that, you can explore the solutions below. If XAMPP’s Apache cannot start, it is very likely that your default HTTP port (80), is blocked or being used by another application. improper privileges, a crash, or a shutdown by another method. This may be due to a blocked port, missing dependencies, When you try to start Apache Web Server, the XAMPP Control Panel will attempt to do so, but end up failing abruptly, mentioning that “Apache shutdown unexpectedly” (like the red text shown in the photo above).īelow is a transcription of the error, with the shutdown message highlighted. The error messages shown when Apache fails to start.
0 Comments
Read More
Leave a Reply. |