Server is accessing port 80 on the internet.
Server is accessing port 80 on the internet.
Hi, I see you're facing an issue where PID 4 is using port 80, which is needed for Apache. Let's resolve this.
It seems another application is already handling the web server.
You can open Task Manager, then click on Resource Monitor from there... You'll have a network tab and you can there expand the Listening ports and you should see there which application listens on port 80 See in the picture how it says Filezilla Server.exe is listening on port 21... that's my local ftp server: If you don't want to use resource monitor ... Open a command prompt with administrative rights right click on cmd and select run as administrator then type : netstat -a -b >c:\temp\output.txt Replace c:\temp with a valid folder on your computer's drives . Run it, wait a few seconds and then press Ctrl+C to stop it (by default, it keeps checking and saving newly created connections to the text file and you don't care about that. Then you can look in the text file and scroll down until you see something like listening and port 80 or http (because http is the default protocol using port 80) For example, here's the start of the text file I get : You can see I have a ftp server running, the application is "Filezilla Server.exe" and it listens on all local IP addresses (hence 0.0.0.0) and the port is 21, default for ftp There's also vncserver.exe (a sort of remote desktop connection server I configured on port 5901 - the default for vnc is 5900, i changed it because i don't want random bots on internet to keep trying passwords on port 5900) So you can just look for 0.0.0.0:80 and see which application uses it. Active Connections Proto Local Address Foreign Address State TCP 0.0.0.0:21 mariushpc:0 LISTENING [FileZilla Server.exe] TCP 0.0.0.0:135 mariushpc:0 LISTENING RpcSs [svchost.exe] TCP 0.0.0.0:445 mariushpc:0 LISTENING Can not obtain ownership information TCP 0.0.0.0:5357 mariushpc:0 LISTENING Can not obtain ownership information TCP 0.0.0.0:5901 mariushpc:0 LISTENING [vncserver.exe] TCP 0.0.0.0:27036 mariushpc:0 LISTENING [Steam.exe] TCP 0.0.0.0:49152 mariushpc:0 LISTENING [wininit.exe] TCP 0.0.0.0:49153 mariushpc:0 LISTENING eventlog [svchost.exe] TCP 0.0.0.0:49154 mariushpc:0 LISTENING Schedule [svchost.exe] TCP 0.0.0.0:49155 mariushpc:0 LISTENING [lsass.exe] TCP 0.0.0.0:49164 mariushpc:0 LISTENING [services.exe] TCP 127.0.0.1:5354 mariushpc:0 LISTENING [mDNSResponder.exe] TCP 127.0.0.1:5354 license:49157 ESTABLISHED [mDNSResponder.exe] TCP 127.0.0.1:7778 mariushpc:0 LISTENING [TracSrvWrapper.exe] TCP 127.0.0.1:7778 license:49193 ESTABLISHED [TracSrvWrapper.exe] TCP 127.0.0.1:14147 mariushpc:0 LISTENING [FileZilla Server.exe] TCP 127.0.0.1:23319 mariushpc:0 LISTENING [qbittorrent.exe] TCP 127.0.0.1:27015 mariushpc:0 LISTENING [AppleMobileDeviceService.exe] netstat /? Displays protocol statistics and current TCP/IP network connections. NETSTAT [-a] [-b] [-e] [-f] [-n] [-o] [-p proto] [-r] [-s] [-x] [-t] [interval] -a Displays all connections and listening ports. -b Displays the executable involved in creating each connection or listening port. In some cases well-known executables host multiple independent components, and in these cases the sequence of components involved in creating the connection or listening port is displayed. In this case the executable name is in [] at the bottom, on top is the component it called, and so forth until TCP/IP was reached. Note that this option can be time-consuming and will fail unless you have sufficient permissions. [...]