XAMPP - Port 80 in use by "Unable to open process" with PID 4! 12

Question

I've tried deleting skype but that didn't work, I've tried turning off the world wide web thing off, IIS off nothing seems to work.

12:51:22 PM  [Apache]   Problem detected!
12:51:22 PM  [Apache]   Port 80 in use by "Unable to open process" with PID 4!
12:51:22 PM  [Apache]   Apache WILL NOT start without the configured ports free!
12:51:22 PM  [Apache]   You need to uninstall/disable/reconfigure the blocking application
12:51:22 PM  [Apache]   or reconfigure Apache and the Control Panel to listen on a different port

No I ment to type it on here, not everyone knows everything about computers. I was asking for help, i've googled it and everything people say to do doesn't work. — user3097839, Dec 13 '13 at 06:31
Ah, this makes more sense now. Try http://www.petri.co.il/quickly_find_local_open_ports.htm to find out who is blocking port 80 — Pekka, Dec 13 '13 at 14:09
@Pekka I've been working with computers since not long after I stopped crapping in diapers, I've been a programmer as well now for almost a decade, and I googled this question and thankfully because the persons asking and answering this question USE this site, I quickly found the answer. Although this probably should be migrated to superuser, badgering people and making them feel stupid for asking a legitimate question is contrary to how this community functions. I suggest you find some other purpose in life. — , Mar 04 '14 at 08:34
Well I'm not sure where this result was produced during your search, but in my search, thanks to this thread, this was top of the list. That's precisely what this community strives to be, a highly visible and well known knowledge base for this kind of stuff. So while I appreciate what you're saying, in reality, mission accomplished thanks to the OP. — , Mar 04 '14 at 17:52
@TechnikEmpire but the fact that this question is now a high-ranking Google result is part of the *problem,* not the solution. The Google result already contained great answers before this question came into existence - I checked before making the comment, I always do. Those answers may now have been pushed down by this question, because of SO's immense clout with Google. See also discussion here: http://meta.stackexchange.com/questions/160565/general-reference-questions-create-low-quality-dead-ends-for-googlers — Pekka, Mar 05 '14 at 19:38
Try `net STOP http` from **PROMPT with ADMIN** is work fine. — KingRider, Jul 28 '16 at 17:54

score 425 · Answer 1 · edited May 17 '18 at 03:56

425

Open a CMD prompt as administrator and execute the following command:
```
net stop was /y
```
Open the Run dialog box (press Win+R), then type: services.msc

Then search for World Wide Web Publishing Service (WWW-Publishing Service) and Web Deployment Agent Service and stop them. You should also disable them.
Start Apache again with XAMPP :)

Link Ref: https://www.sitepoint.com/unblock-port-80-on-windows-run-apache/

edited May 17 '18 at 03:56

Pang

9,564
146
81
122

answered Feb 27 '14 at 03:42

Vo Quoc Cuong

4,448
1
14
6

17

I can't find world wide web – Mohammad Kermani Jul 07 '14 at 08:07
4

Another way to get access to the services - go to `Control Panel > System and Security > Administrative tools > Services` – Al.G. Jan 31 '15 at 18:55
29

"SQL Server Reporting Service(MSSQLSERVER)" also uses port 80 and so it should be stopped if MS-SQL sever is insalled on your machine. – johnkarka Nov 21 '15 at 12:01
2

Any idea why this might occur? Is it Windows being douchey, or someone hacking my machine? – Stan Quinn Jul 26 '16 at 03:35
Nice solution. After stop that service. What can be side effects of it? – Bhavin Thummar Nov 08 '20 at 13:42
Thanks @vo-quoc-cuong, step2 worked for me. – Shamsul Haque Jul 28 '23 at 12:49

gtr1971 · Answer 2 · 2014-10-30T03:14:24.113

155

Another very easy option is to simply set Apache to listen on a different port. This can be done by clicking on the "Config" button on the same line as the "Apache" module, select the "httpd.conf" file in the dropdown, then change the "Listen 80" line to "Listen 8080". Save the file and close it.

Now it avoids Port 80 and uses Port 8080 instead without issue. The only additional thing you need to do is make sure to put localhost:8080 in the browser so the browser knows to look on Port 8080. Otherwise it defaults to Port 80 and won't find your local site.

This will also require you to restart Apache for the change to take effect.

Voila! Fixed.

edited Oct 30 '14 at 03:14

answered Mar 12 '14 at 15:58

gtr1971

2,672
2
18
23

I got force upgraded to Windows 10 and it broke my XAMP install, this answer fixed it for me. Thanks! – Ian Jun 16 '16 at 04:19
This worked for me too, except I exited out of everything, clicked on xampp_start in `C:/xampp` and then changed it to port 81. 8080 didn't work for me. – user3553260 Oct 04 '16 at 20:41
2

I recommend your solution. In my case I need to develop ASP .NET Application and PHP. If i stop `World Wide Web Publishing Service` i can't work on my ASP application. SO changing the port is solution for me. Thanks! – mihkov Nov 17 '16 at 13:44
3

In additional the httpd.conf file, you may also need to also change the port from "Config" > "Service and Port Settings". On the "Apache" tab, change the "Main Port" value to the new port – Ian A Jun 21 '17 at 08:23

Ogglas · Answer 3 · 2016-01-06T16:27:11.757

52

In httpd.conf change the following lines and then restart the application:

Listen 80 to Listen 8080
ServerName localhost:80 to ServerName localhost:8080

When you press "Start" the application can still say that you have an error like "Port 80 in use by "Unable to open process" with PID..." but it will still work.

If the error includes "Port 443 in use by "Unable to open process" with PID..." you need to change both httpd.conf and httpd-ssl.conf.

In httpd-ssl.conf change:

Listen 443 to Listen 4433
<VirtualHost _default_:443> to <VirtualHost _default_:4433>
ServerName www.example.com:443 to ServerName www.example.com:4433

edited Jan 06 '16 at 16:27

answered May 22 '15 at 06:30

Ogglas

62,132
37
328
418

I ended up having to do this on my issue. goodness! that PID is by the system. – mzimhle Dec 27 '19 at 13:33
Indeed. After I change port, and then close XAMPP and reopen it still shows red error message, however everything works. Apparently, XAMPP does not check if port has been reconfigured before displaying that error message.It only checks if port is in use. – Vanity Slug - codidact.com Mar 29 '21 at 17:12

score 43 · Answer 4 · edited Jun 24 '17 at 20:23

43

Extracted from this article:

Go to your run command and enter:

netstat -o -n -a | findstr 0.0:80

The last number here is the process ID using it. This is most often IIS or other web relates service and is easy to resolve, but every so often (very often it would seem looking around on google) it appears to be PID 4 – which according to the Windows Task Manager is the NT Kernel and System. Not very helpful given killing this will result in a blue screen of death.

The thing hogging port 80 has nothing to do with IIS or web anything, it's SQL Server Reporting Services. Turn off anything that resembles a SQL Server Services and start Apache again, no need for a reboot.

So problems with PID 4 listening to port 80? Check your SQL services and turn them off.

UPDATE - Comment from @sangam:

Worked at a shot. In my case, it turned out to be SQL server reporting services. I stopped the service for all the installed instances, and it worked (without machine reboot).

edited Jun 24 '17 at 20:23

Richard

4,341
5
35
55

answered Mar 08 '14 at 00:47

chridam

100,957
23
236
235

7

Worked at a shot. In my case, it turned out to be SQL server reporting services. I stopped the service for all the installed instances, and it worked (without machine reboot). Thank you. – Sangam Uprety Sep 25 '14 at 14:48
1

Very helpful.. before this, i changed skype port. and the closing the sql services helped me alot. Thanks alot – Waqar Sep 29 '15 at 18:56
2

finally, in my case it was MSSQL too – Tomas Ramirez Sarduy May 08 '16 at 05:37
1

stopping SQL Server Reporting Services (MSSQLSERVER) worked for me – Disturb Oct 25 '17 at 19:18
1

Thanks this was the answer for me. – balron Jan 15 '20 at 12:50

score 38 · Answer 5 · edited Dec 02 '16 at 03:21

38

So I have faced the same problem when trying to start Apache service and I would like to share my solutions with you. Here are some notes about services or programs that may use port 80:

Skype: Skype uses port 80/443 by default. You can change this from Tools -> Options -> Advanced -> Connections and disable the checkbox "use port 80 and 443 for addtional incoming connections".
IIS: IIS uses port 80 be default so you need to shut it down. You can use the following two commands: net stop w3svc, net stop iisadmin.
SQL Server Reporting Service: You need to stop this service because it may take port 80 if IIS is not running. Go to local services and stop it.
VMware Workstation: If you are running VMware Workstation, you need to stop the VMware Workstation server - port 443 as well.

These options work great with me and I can start Apache service without errors.

The other option is to change Apache listen port from httpd.conf and set another port number.

Hope this solution helps anyone who faces the same problem again.

edited Dec 02 '16 at 03:21

felipeptcho

1,377
2
9
23

answered Oct 28 '14 at 11:05

Peter T.

8,757
3
34
32

4

Mine was the SQL Server reporting service. Thanks! – Jayanga Kaushalya Feb 06 '15 at 21:23
stopping w3svc fixed my problem on windows 10. Great answer. – Nox May 02 '17 at 13:44
How can you tell which services are using port 80? (Windows 10) – Chris Nielsen Jun 01 '17 at 21:02
For me this worked "IIS: IIS uses port 80 be default so you need to shut it down. You can use the following two commands: net stop w3svc, net stop iisadmin" – Ravindra Singh Nov 01 '17 at 16:54

score 33 · Answer 6 · edited Oct 07 '14 at 12:25

33

You might need to stop the "Web Deployment Agent Service"

Press Win+R and type services.msc

Right click on Web Deployment Agent Service and select "Stop"

Restart XAMPP

Also after double clicking "Web Deployment Agent Service" you can make the Startup type to Manual, So that "Web Deployment Agent Service" will not start automatically

edited Oct 07 '14 at 12:25

Jerry Abraham

1,039
18
42

answered Mar 04 '14 at 15:18

Stephen Burrows

470
5
5

1

Is there may be any issue by disabling that service? – Muhammad Muazzam Nov 21 '15 at 10:09

score 10 · Answer 7 · answered Feb 12 '19 at 07:16

As there is comment by @johnkarka on the question, this port is used by SQL Server reporting service as well. After stopping this, Apache started fine.

Go to "SQL Server Configuration Manager"
Click on "SQL Server Reporting Service" and stop it

The funny thing is IIS was working fine in same configuration but not Apache, had to stop SQL Reporting service to make it work on default port (80).

score 9 · Answer 8 · answered Mar 22 '20 at 20:13

9

After changing the main port 80 to 8080 you have to update the port in the control panel: Then click here: And here: Then save and restart.

answered Mar 22 '20 at 20:13

Zeke

562
4
14

score 7 · Answer 9 · answered Sep 30 '15 at 21:43

7

Open Task Manager (Ctrl+Alt+Delete).
Go to "Details" tab.
Sort by PID number.
End process that is using PID number indicated in error.
Restart XAMPP.

answered Sep 30 '15 at 21:43

wmcnally

147
2
14

2

In my case, it is the system who is using PID4. Therefore this can be dangerous. – Fusion Mar 08 '16 at 11:38
worked for me as port was used by my other server. And consider @Fusion's comment too – Varshaan Jun 07 '16 at 08:16

score 4 · Answer 10 · answered Mar 05 '14 at 05:25

What worked for me was stopping the Internet Information Services (IIS). If you are using Windows 7, click on your Start button and in your search box, type "iis". Click on "Internet Information Services (IIS) Manager". When the window pops up, and assuming you've got none of the icons selected, you should just be able to click Stop on the right action pane. My XAMPP Apache started right up. Hope it all worked out for you.

score 3 · Answer 11 · answered Oct 12 '16 at 11:41

3

In windows 10, to free up port 80:

in my case, I open "Services" from "Search Windows" (on the left corner on screen), then stop all of SQL server services MSSQLSERVER and it works again

answered Oct 12 '16 at 11:41

N.P

54
2

score 3 · Answer 12 · answered May 19 '17 at 16:27

I had this problem too and stoping services using port 80 didn't helped. I resolved it by following this procedure (found on a french board):

Launch RegEdit
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP
Change the value of "start" to 4 (disabled)
Reboot your computer

Not sure how this affect other services, but it solved permanently the issue and so far I didn't see any issue.

Using Windows 10.

score 2 · Answer 13 · answered Mar 19 '14 at 00:29

2

If you've SQLServer Reporting Services running locally then you need to stop that also..

answered Mar 19 '14 at 00:29

Senthil

1,499
16
17

score 2 · Answer 14 · answered Aug 17 '14 at 11:46

I've had the same problem, but in my case Apache was already running and for some reason the XAMPP config tool didn't show that. It happened after I started XAMPP for the first time after the installation. After crashing the other Apache instances all was fine and ports 80 and 443 were free again.

So before making changes to your systeem, make sure something as obvious as the above isn't happening.

score 2 · Answer 15 · answered Aug 05 '17 at 10:32

2

"SQL Server Reporting Service" was causing issues in my system, after stopping it, Apache started working fine

answered Aug 05 '17 at 10:32

ramya

2,350
6
31
57

score 2 · Answer 16 · answered Oct 24 '17 at 07:01

2

I have the same issue, I solved the problem, just disabled

"BranchCache Service" in services.

Somehow windows updates, this service is triggered in startup, and uses 80 ports. When you check via netstat you could see the system is used this but couldnt understand which service is used.

answered Oct 24 '17 at 07:01

Günay Gültekin

4,486
8
33
36

1

Disabling this service after every windows 10 update resolves the issue – Matt Jun 18 '19 at 10:09

score 1 · Answer 17 · answered Jun 12 '15 at 01:02

1

Click services on the Xampp control panel (filename is services.msc, extra info).

First, look for IIS, if it is running. Stop it (stop this service option on the left after clicking on the service name.). Then, this is the main problem, Look for Web deployment Service (not the exact name though it has Web deployment at the beginning.). Stop this service too. Try again and Apache should work.

If you are running Skype, exit out of that too, run Apache, then launch Skype

answered Jun 12 '15 at 01:02

rassa45

3,482
1
29
43

Normally, Skype hogs up port 80 but is smarter than XAMPP and will use a different port once it realizes that 80 belongs to Apache Server – rassa45 Jun 12 '15 at 01:03

score 1 · Answer 18 · answered Dec 19 '16 at 19:20

I've had same problem, when I was installed MS WebMatrix, IIS Server was blocked the port 80 which XAMPP was running on. I tried to find World Wide Web Publishing Service and stop it, but could not find it on list. Best way is changing a port.

Please refer with this
link ref.

score 1 · Answer 19 · answered Aug 10 '18 at 02:54

1

For those with ASP.NET, C# or having SQL Server users, If you are using SQlServer OR Visual Studio Your port might encounter. easiest thing you might want to do is on Command> servies.msc and then find SQl Server Reporting Service and then stop it.

answered Aug 10 '18 at 02:54

Suman Thapa Magar

201
3
7

score 0 · Answer 20 · answered May 21 '14 at 09:06

0

if the service is http.sys

You need to change the binded IP address for http.sys

netsh http add iplisten ipaddress=::

Work fine without restart the os.

answered May 21 '14 at 09:06

mik3fly-4steri5k

712
3
15
32

score 0 · Answer 21 · answered Oct 17 '14 at 20:33

0

The Web Deployment Agent Service is deployed with WebMatrix and was the cause of my woes. It may also be distributed with other applications installed using Microsoft’s Web Platform Installer.

Uninstall it solved my problems!

answered Oct 17 '14 at 20:33

brunodotcom

21
7

Nope, just change port that server listens on. – rango Dec 20 '16 at 12:17

score 0 · Answer 22 · answered Nov 22 '14 at 15:58

0

For me usually works: - Turn off Skype - Turn off all SQL Server processes displayed in services.msc - Turn off World Wide Web Publishing in services.msc

answered Nov 22 '14 at 15:58

Iwona Kubowicz

364
3
15

score 0 · Answer 23 · answered Dec 19 '14 at 07:04

0

It usually works afters you stop IIS Server and Skype

answered Dec 19 '14 at 07:04

N A

831
2
8
28

score 0 · Answer 24 · answered Jan 01 '16 at 16:10

XAMPP - Port 80 in use by “Unable to open process” with PID 4! 12

run the comment in cmd tasklist

and find which the PID and process name related to this now open window task manager

you can also open window task manager by using CTRL+ALT+DEL

now click on the process tab and find the name which using PID and right click on that and end process

now again restart the xampp

Hossein Khalesi · Answer 25 · 2018-08-29T12:40:05.403

I had same issue. After some googling arrived to this page. Since I guess this error may have various reasons, so listen to my experience:

Xampp red line log:

12:53:54 PM  [Apache] Problem detected!
12:53:54 PM  [Apache]   Port 443 in use by "Unable to open process" with PID 3908!
...

Finally it turned out that I had this line of code in my php codes :

$res = file_get_contents("http://$_SERVER[HTTP_HOST]$_SERVER[REQUEST_URI]");

The purpose of this piece of code was to get a mirror of php result from somewhere in my server. But it's just stucked in a loop that gets its own content!

I repaired code:

$res = file_get_contents(str_replace("my_uri.php" , "mirror_uri.php" , "http://$_SERVER[HTTP_HOST]$_SERVER[REQUEST_URI]"));

Then I restarted apache ... and that apache error never happened again.

So sometimes searching for probable halting points in your code is a good approach.

score 0 · Answer 26 · answered Sep 04 '19 at 07:45

0

In Ubuntu by default, the system will not allow you to occupy privileged ports [ 0 to 1023], other than specifying the port as 80, you need to run XAMP with sudo.

answered Sep 04 '19 at 07:45

Arun Joseph

2,736
25
35

score 0 · Answer 27 · answered Jun 16 '23 at 22:41

This solution works for me.

I am on Windows 11 and I have a port 80 issue because of Nginx server was running on port 80.

These are the steps that I have followed to resolve the issue.

Go to Shell from XAMPP Control Panel
Run this command to stop Nginx Server @taskkill /f /im nginx.exe
After the success message you can close the shell window and restart the Apache server.

score 0 · Answer 28 · answered Aug 06 '23 at 15:26

By default, XAMPP will check default ports on startup, even if you have already changed Apache's default listening port in "C:\xampp\apache\conf\httpd.conf" to anything other than port 80;

To prevent it:

Go to XAMPP Control Panel > Config
Uncheck "Check default ports on startup"

score -1 · Answer 29 · edited Jan 21 '16 at 22:08

I write this, because i coudn't find answear for the same question. In my case PID was 2484.

you must find a process or service with this PID: open cmd (in Windows) and write:
```
tasklist
```
Find your PID in this list and read name of process or service.
Now you can kill this using Task Manager
find this name on Process list
click End Process.

That's my case. Possibly you must open services.msc and stop Service with your PID.

On my computer xampp it worked fine :)

XAMPP - Port 80 in use by "Unable to open process" with PID 4! 12

29 Answers29

Linked

Related