[Page 1, 2 Next]

Topic: Apache2.4.16 won't start

[1]

Topic: Apache2.4.16 won't start

[Markus_Aurelius]

I just unzipped Apache 2.4.16 VC14 to apache24. I am running windows 10 64-bit. I have visual studio 2015 redist. installed for x86 and x64. I don't have any php installed yet. I just want to get apache running. Running apachemonitor does not start apache.
I ran command with admin privileges and cd'ed to apache/bin. httpd to start apache. I got errors.
The error is: An attempt was made to access a socket in a forbidden way by its access permission. :AH00072: make sock could not bind to address [::]:80.
And this one is ipv4: An attempt was mad to access a socket in a forbidden way by its access permission. :AH00072: make sock: could not bind to address 0.0.0.0.:80.
Then there is AH451 no listening sockets available.
AH00015 Unable to open logs.
There is also determing servername error how can this one also be fixed?

[daniel1975]

Check if you have Skype launched, as default configuration values "Tools" menu, "Options..." command, then "Advanced" section from left then "Connection" followed by first check box from top named "Use 80 and 443 for additional incoming connections", therefore occupying these ports. Coupled with default setting "Start Skype when I start Windows" really makes an annoying combination that I bumped in early days.

If that is not the case you might wanna try "netstat" from command prompt.

[Markus_Aurelius]

skype has been removed. Skype has a history of causing problems with lots of software.

[Jan-E]

run 'netstat -anb' in a command prompt to see which program is listening to port 80.

[Markus_Aurelius]

I don't have apache installed as a service. httpd -k start causes the errors.

[Jan-E]

The error message is caused by the fact that another program is already listening to port 80. netstat -anb tells you which program that is.

[Markus_Aurelius]

A couple of days ago I had to reinstall windows 8.1 because Microsoft Edge got hit with ransom-ware. It has taken me this long to get it installed and working correctly.
I managed to get an earlier version of Apache working. Version was an msi, 2.2. I really liked that there were msi installers, they almost always worked.

I ran a netstat -anb to see what was there. Apache is running on port 135. The netstat output is [::]:135. Explorer.exe is [::]:80 should I change this?
The goal is to get Apache 2.4.16 running and php 5.6 or 7 RC3. I want to run a couple of websites and would like to be able to be certain that this is going to be stable.
By the way the version of Apache that is currently running is a 32-bit version. The version of Apache that is the goal is going to be a 64-bit. Is this going to create a problem opening a zip file onto this folder?
Also I plan to put Windows 10 back on this computer. Any problems there?

[Jan-E]

I have never seen exlorer.exe listening on port 80, but it seems to happen. Skype is a known culprit for using port 80, but IIS and SQL Server Reporting Service come seconf best.

Are you sure Skype is disabled? Windows 8.1 originally had 2 versions: an app and a desktop program.

Otherwise, read:
http://stackoverflow.com/questions/23317372/xampp-port-80-in-use-by-unable-to-open-process-with-pid-4
http://www.devside.net/wamp-server/opening-up-port-80-for-apache-to-use-on-windows

[Markus_Aurelius]

I got it running but have a new problem. Have to switch over to php.
Thanks for your help.
By the way, there is no skype whatsoever on my machine. I always get rid of it.

[otto58]

I have the same problem with Win10 32bit.
The problem starts at night as Win10 makes a restart for update (KB3093266). Uninstalling the update does not help.

Here information about port 80:

[AllShareFrameworkDMS.exe]
TCP 192.168.10.20:80 192.168.10.20:54051 WARTEND
TCP 192.168.10.20:80 192.168.10.20:54052 WARTEND
TCP 192.168.10.20:80 192.168.10.20:54089 WARTEND
TCP 192.168.10.20:80 192.168.10.20:54090 WARTEND
TCP 192.168.10.20:139 0.0.0.0:0 ABHÖREN

[otto58]

I think you mean this

Proto Lokale Adresse Remoteadresse Status
TCP 0.0.0.0:21 0.0.0.0:0 ABHÖREN
[FileZilla Server.exe]
TCP 0.0.0.0:80 0.0.0.0:0 ABHÖREN
Es konnten keine Besitzerinformationen abgerufen werden.
TCP 0.0.0.0:111 0.0.0.0:0 ABHÖREN
[FreeNFS.exe]
TCP 0.0.0.0:135 0.0.0.0:0 ABHÖREN

No information about the user of port 80.

[otto58]

I run in the problem (during Win 10 update) with "Win32-2.4.9 VC11 update 4"
Then I have changed to "Win32-2.4.16 VC14". But the problem with port 80 is remainig.

On an other maschine, with the Win10 update, a new installed "Win64-2.4.16 VC14" runs without problems.

Is there a chance to remove all old things from the 32 bit machine for a clean Apache installation?

[James Blond]

open a command line ( cmd.exe) as Administrator

run

[Markus_Aurelius]

Last week I got some ransomware in Edge. I reinstalled to get Edge working again. This meant going back to Win 8.1 While in 8.1 I installed an older version of apache with an msi installer. The version was 2.2.x. It installed without headache. Since that work, I then installed PHP 5.2.9. I have not had any problems with this ever.
I tested with phpinfo() and everything was ok. The I unzipped Apache 2.4.16 64-bit without the httpd.conf file. I ran localhost only. "It Works" So with good luck so far I tried PHP 5.6 64-bit. I ran phpinfo again and it came up with php 5.6 is running and apache 2.4 was the server. Success! So I play around with it a bit. Then I installed Windows 10 Home. It still worked.
The thing I like is that the msi versions seemed to always work. I don't know why they don't make them like that anymore. It is way to much of a headache to unzipped them and install.
You need to add httpd.exe to windows firewall and add the ports 80 and 443 to the firewall to get them to work. The installer manages to take care of such things. Although the firewall usually says any.
However, now I am wondering what problems I will have when I take my website live?

[isma_5]

I'm using:
- Windows 10 64bits
- Apache 2.4.16
- php-5.6.14-src

When I use the command "httpd -k install" it gives the following error:

Installing the 'Apache2.4' service
The 'Apache2.4' service is successfully installed.
Testing httpd.conf....
Errors reported here must be corrected before the service can be started.
AH00526: Syntax error on line 1 of C:/Apache24/conf/httpd.conf:
Invalid command '\xff\xfe#', perhaps misspelled or defined by a module not included in the server configuration

After following all the installations process, when I start Apache 2.4 it displays an error message saying:
"This requested operation has failed"

[James Blond]

'\xff\xfe#

You saved the file UTF-8 with BOM. Save it without BOM and it shall work.

[Zayde]

I am having the same problem as many other people.
I have successfully installed http-2.4.17-win64-VC14 as a service.
I opened cmd.exe as Administrator and tried httpd -k start and got the familiar error message:

Could not reliably determine the server's fully qualified domain name, using fe80::f53e:d8dc:2634:dcf1. Set the 'ServerName' directive globally to suppress this message
(OS 10013)An attempt was made to access a socket in a way forbidden by its access permissions. : AH00072: make_sock: could not bind to address [::]:80
(OS 10013)An attempt was made to access a socket in a way forbidden by its access permissions. : AH00072: make_sock: could not bind to address 0.0.0.0:80
AH00451: no listening sockets available, shutting down
AH00015: Unable to open logs

Here is the Servername line in my httpd.conf:
ServerName 192.168.1.3:80 This is my desktop ip on my local network as given by Netgear Genie. Everything is on the same PC.

I know that NT Kernel & System is using port 80.
Does that explain everything here ? If so, what can I do about it ?

[Zayde]

I found that in unzipping the package I had to do redo it, and ended up with two sets of files. I was editing one conf file, and then running the other .
Sorry !

Still a problem - it is installed and started, but I don't get a response from localhost. I'll check firewalls, filters, etc.

[Zayde]

I was running into port 80 conflicts, so I edited the conf file to
Listen 1234
and Servername localhost

If I enter 'localhost:1234' I get the 'It's working !' response, but just 'localhost' does not respond.

This is a pain. How can I set up a shorter identifier to get to the server ?

[glsmith]

The only way to do that is get port 80 open so Apache can run on that port which is the default for http. You can find what is using port 80 from the command line with netstat -b