XAMPP Error: Apache shutdown unexpectedly.This may be due to a blocked port, missing dependencies…

Problem: When setting up a station via XAMPP, Apache does not start successfully and reports the following error.
10:02:35  [Apache] Error: Apache shutdown unexpectedly.
10:02:35  [Apache] This may be due to a blocked port, missing dependencies,
10:02:35  [Apache] improper privileges, a crash, or a shutdown by another method.
10:02:35  [Apache] Press the Logs button to view error logs and check
10:02:35  [Apache] the Windows Event Viewer for more clues
10:02:35  [Apache] If you need more help, copy and post this
10:02:35  [Apache] entire log window on the forumsThis is a common problem, and the reason for this error is that the common ports, including http and https, are occupied by XAMPP’s settings, solution.
cmd by running apache/bin/httpd.exe Print the following log.
(OS 10048) Normally each socket address (protocol/network address/port) is allowed to be used only once. : make_sock: could not bind to address 0.0.0.0:443
Or maybe port 80 is occupied.
(OS 10048) Normally each socket address (protocol/network address/port) is allowed to be used only once. : make_sock: could not bind to address 0.0.0.0:80 or [ : : ]:80
Solution 1: The fastest way to handle this is to change the port number.
1, port 443 is occupied, apache can not listen to port 443, how to solve it?
In /xampp/apache/conf/extra/httpd-ssl. conf
Change Listen 443 to 444 (customizable)
2, port 80 is occupied, apache can not listen to port 80, how to solve it?
In /xampp/apache/conf/extra/httpd. conf
Change Listen 80 to 88 (customizable)
If you have configured vhosts, please change the port in httpd-vhosts.conf to 88 (same port number as above).

Solution 2: The most straightforward method is to shut down the processes that occupy ports 80 and 443.
1. see if the local ports 80 and 443 are occupied by netstat -ano in cmd —– – here it may be occupied by other programs such as iis, virtual machine, etc.
2. print tasklist in cmd to find the name of the process that occupies port 80 and 443. 3. taskkill /pid port number to kill the process name.
3. taskkill /pid port number kill this process name, XAMPP restart apache can be.
In summary, the first method is recommended, and the second is more or less every time you start up again.

Read More: