logo
Apache Lounge
Webmasters

 

About Forum Index Downloads Search Register Log in RSS X


Keep Server Online

If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.

or

Bitcoin

A donation makes a contribution towards the costs, the time and effort that's going in this site and building.

Thank You! Steffen

Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
Post new topic   Forum Index -> Apache View previous topic :: View next topic
Reply to topic   Topic: Apache can't access ports despite them being open
Author
BeautifulAttackHelicopter



Joined: 13 Aug 2016
Posts: 2

PostPosted: Sat 13 Aug '16 13:39    Post subject: Apache can't access ports despite them being open Reply with quote

Stats:
Windows 7 64bit
WAMP 3.0.4 64bit
Apache 2.4.18
MySql 5.7.11
PHP 5.6.19


I can't for the life of me make apache play nice with my port. Even though when using WAMP's "test port 80" it :

Quote:
Your port 80 is actually used by :

Server: Apache/2.4.18 (Win64) PHP/5.6.19


Apache keeps giving me this error twice:
Quote:
(OS 10048)Only one usage of each socket address (protocol/network address/port)
is normally permitted. : AH00072: make_sock: could not bind to address [::]:80
(OS 10048)Only one usage of each socket address (protocol/network address/port)
is normally permitted. : 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



According to http://wiki.apache.org/httpd/CouldNotBindToAddress there are three common causes for port problems. I do not have Skype, SELinux or AppArmor, not using linux (am admin so i dont need root) and all my listen directives are commented except one directive. Here are the errors:

http://apaste.info/8ch


I have uninstalled and installed, used different ports, tried using only ipv4 or ipv6 - nothing works. netsh -ano shows the PID of apache using port 80, but apache still gives errors for port 80.


I am completely and utterly clueless since I have tried every solution I could find in the documentation.


Recent error logs:
http://apaste.info/jVM

Access logs:
http://apaste.info/2sY
Back to top
glsmith
Moderator


Joined: 16 Oct 2007
Posts: 2268
Location: Sun Diego, USA

PostPosted: Sun 14 Aug '16 4:02    Post subject: Reply with quote

Crazy is, there is one other option and the only reason I bring it up is because Wamp is telling you Apache is using port 80. I don't think it would know that unless Apache was already running. Check the Task Manager in Windows and look for two httpd.exe listed. When Apache is running on Windows there will be two listed, this is normal.
Back to top
Jan-E



Joined: 09 Mar 2012
Posts: 1266
Location: Amsterdam, NL, EU

PostPosted: Sun 14 Aug '16 18:55    Post subject: Reply with quote

Try 'netstat -anb' in a command prompt with admministrator rights to see which program is listening to port 80.
Back to top
BeautifulAttackHelicopter



Joined: 13 Aug 2016
Posts: 2

PostPosted: Fri 19 Aug '16 13:30    Post subject: Reply with quote

glsmith wrote:
Crazy is, there is one other option and the only reason I bring it up is because Wamp is telling you Apache is using port 80. I don't think it would know that unless Apache was already running. Check the Task Manager in Windows and look for two httpd.exe listed. When Apache is running on Windows there will be two listed, this is normal.


It does not list two. However when it DOES list two httpd.exe, killing one just kills both. It's an infinite loop where to activate httpd you have to kill httpd to free a port for httpd.


Tell me, should WAMP suck that much? Aren't there other, sane solutions to setting up your server?
Back to top
glsmith
Moderator


Joined: 16 Oct 2007
Posts: 2268
Location: Sun Diego, USA

PostPosted: Fri 19 Aug '16 17:56    Post subject: Reply with quote

Two processes is normal. One is the Parent and one the Child, it's how it works on Windows. But if Apache is already running and you try to start another instance it will fail because the first instance is using port 80.
Back to top


Reply to topic   Topic: Apache can't access ports despite them being open View previous topic :: View next topic
Post new topic   Forum Index -> Apache