Windows server 2008 r2 – can’t get apache to run on port 80

apachewindows

I have a rackspace cloud server running windows server 2008 r2. I've uninstalled IIS because I want to install Apache.

I've installed Apache but it fails everytime i try to run it when i listen to port 80.

I've run the command netstat -aon|finderstr "80" and i see the following:

C:\Users\Administrator>netstat -aon|findstr "80"
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 4
TCP 10.180.15.249:139 0.0.0.0:0 LISTENING 4
TCP [::]:80 [::]:0 LISTENING 4
UDP 10.180.15.249:137 : 4
UDP 10.180.15.249:138 : 4

So what are these things running on port 80 and why can't i get apache to start? Is there an alternative port for to run apache under that will work just as well as 80?

Best Answer

To enable port 80 on Windows Server 2008 R2:

NOTE: This assumes that IIS is not installed. I added this firewall rule to enable Apache to accept connections on port 80.

Click Start->Control Panel->Windows Firewall
Click "Advanced Settings" in the left panel of Windows Firewall
Click "Inbound rules" in the left panel of Advanced Settings
Click "New Rule..." in right "Actions" panel
Select "Port" and click "Next>"
Select "TCP", then "Specific local ports:" (should already be selected)
Type 80 in the box (just the number) and click "Next>"
Select "Allow the connection" and click "Next>"
Leave all profiles checked and click "Next>"
Enter a name and click "Finish".

Your server should now be able to accept connections on port 80.

New answer, powershell

TCP

Get-Process -Id (Get-NetTCPConnection -LocalPort YourPortNumberHere).OwningProcess

UDP

Get-Process -Id (Get-NetUDPEndpoint -LocalPort YourPortNumberHere).OwningProcess

Old answer, cmd

 C:\> netstat -a -b

(Add -n to stop it trying to resolve hostnames, which will make it a lot faster.)

Note Dane's recommendation for TCPView. It looks very useful!

-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.

-n Displays addresses and port numbers in numerical form.

-o Displays the owning process ID associated with each connection.

Windows – How to run Redis on Windows

Download Microsoft's port from their GitHub repository.

This release includes the redis-server.exe application that runs a Redis instance as a service on your windows machine, as well as redis-cli.exe which you can use to interact with any Redis instance.

The RGL repository has historically been listed as an alternative Windows port for Redis, but this repository has not been maintained for some time and implements an older version of Redis than the Microsoft port.

It should be noted that the official port is no longer maintained either, and Microsoft recommends yet another alternative for the latest Redis features. However, their recommendation is neither free nor open source, so it won't be linked here.

Best Answer

Related Solutions

Windows – How to you find out which process is listening on a TCP or UDP port on Windows

New answer, powershell

TCP

UDP

Old answer, cmd

Windows – How to run Redis on Windows

Related Topic