Apache error - cound not bind to address 0.0.0.:80

September 21st, 2004, 2:55 pm

I'm new to server stuff and I've just install Apache so I can learn PHP. I'm running Windows XP w/SP 2 installed.

When I start Apache, I get the error message:

Only one usage of each socket address (protocol/network address/port) is normally permitted. :make_sock: could not bind to address 0.0.0.:80
Unable to open logs.

I think it means something else on my machine is using port 80.

1) How do I find out what else is using port 80?

2) I found something about a conflict with Apache & IIS (Internet Information Service) webserver but don't know anything about IIS .
> How do I check to see if I have that on my PC?
> If it's on my PC how do I disable it?

2) Is there another port I can use for Apache?
If so,
> What other ports are available?
> Do I only have to change the port number in the 'Servername=' parameter in the Configuration file?

I'd appreciate assistance on this so I can proceed with learning PHP. Thanks!

September 21st, 2004, 3:19 pm

Hi, Chuck, Welcome to Ozzu. I don't use Apache but someone else can help you with that, don't worry, there's a lot of friendly and skilled people here (I am the black sheep )

To stop IIS try this

1- Goto control panel > Administrative Tools > Internet Information Service (IIS) Manager
2- In IIS Manager, right click the local computer, point to All Tasks, then click Restart IIS
3- In the What do you want IIS to do list, select Stop Internet Services on <yourcomputername>

Your account must be an administrative account to do this.

//EDIT: I also found this about changing conf file on Apache to avoid this error:

Quote:

Open up your httpd.conf file in apache2/conf, look for the line that starts with Listen usually around line number 120 or so.See that it is set up to Listen on 80 or whatever port you wanted, look for ServerName line and put either localhost or 127.0.0.1, save the file and check again

September 21st, 2004, 6:34 pm

If the 0.0.0:80 in your error message is not actually a typo in the forum message, then you could look for 0.0.0 in the httpd.conf file too - it is a bogus IP address and if the config file actually contains that as a bind address it will certainly fail

September 21st, 2004, 11:28 pm

Thanks for your input Finndel, Chuck already solved his problem, here's a PM he sent me:

Chuck wrote:

Apache is working!! I noticed the icon in my system tray that indicated 'Running all Apache Services'. I must have started Apache and didn't know it????

Maybe that's why I got that error since port 80 was already being used by the 1st instance of Apache ?

Anyway, I had changed the servername to 'localhost' (with no :80), then went to my browser and entered 'localhost' in the url and got the default start page!

Thank you for your suggestions! Forums like this are what makes the Internet GREAT!

Chuck

September 21st, 2004, 11:45 pm

Cool, glad he's sorted

Steve.

June 29th, 2005, 2:35 pm

This was great help to me as well. Thank you!!

June 29th, 2005, 2:40 pm

You are welcome redcreative, glad we can help you. And BTW, welcome to Ozzu.

July 6th, 2005, 7:09 am

I am replying here because I had the same problem, but fixed it with your solution here.

However,
I am able to access it locally (localhost or 127.0.0.1)
but I cannot access it within my local lan, (on the router)
and also I cannot access it outsite the lan.

I changed the port to 81 to see if that would make a difference, but no dice

Any Suggestions?

Btw:
Windows 2000
No Firewall Installed.

I am fairly sure that for some reason the port doesnt seem to be available to other comptuers.

July 6th, 2005, 7:43 am

For those experiencing similar problems:

I was able to resolve this by changing from localhost/ 127.0.0.1
to my internal IP (192.168.1.3)

Now it works fine.

I dont suppose anyone can explain this to me?

Sometime I think computers do things to mess with us.

July 29th, 2007, 6:09 am

hi guys,

i am totally new to apache n all.....
i am having the same problem and tries all the things as mentioned in the above posts....
but none of them seem to work and i get the sam error...is there anything else i can do?

thanks

July 29th, 2007, 6:38 am

hey guys hi again..

well i got that issue taken care of...i had made a typo..

now the problem is when i type http://localhost in the browser i get an error..

in Internet Explorer the error is: HTTP 403: The website requires you to login.

and in Mozilla Firefox the error is:
Forbidden
You do not have permission to access / on this server.

Can you kindly help me out with the problem..I will realyy appreciate it..
Thanks

March 21st, 2008, 8:12 am

With reference to the question above,

I was getting the following error:

Installing the Apache2.2 service
The Apache2.2 service is successfully installed.
Testing httpd.conf....
Errors reported here must be corrected before the service can be started.
httpd.exe: Could not reliably determine the server's fully qualified domain na
, using xxx.xxx.xxx.xx for ServerName
(OS 10048)Only one usage of each socket address (protocol/network address/port
is normally permitted. : make_sock: could not bind to address 0.0.0.0:xxxx
no listening sockets available, shutting down
Unable to open logs
Note the errors or messages above, and press the <ESC> key to exit. 14...

The trick, I found, was to edit the configuration files, and add listen <ipaddress>:<port>

where <ipaddress> is the public IP address of the server, not the loopback address.

January 20th, 2010, 3:55 am

dananos wrote:

With reference to the question above,

I was getting the following error:

Installing the Apache2.2 service
The Apache2.2 service is successfully installed.
Testing httpd.conf....
Errors reported here must be corrected before the service can be started.
httpd.exe: Could not reliably determine the server's fully qualified domain na
, using xxx.xxx.xxx.xx for ServerName
(OS 10048)Only one usage of each socket address (protocol/network address/port
is normally permitted. : make_sock: could not bind to address 0.0.0.0:xxxx
no listening sockets available, shutting down
Unable to open logs
Note the errors or messages above, and press the <ESC> key to exit. 14...

The trick, I found, was to edit the configuration files, and add listen <ipaddress>:<port>

where <ipaddress> is the public IP address of the server, not the loopback address.

I was having the exact same issue and this worked for me, too. I don't know why the .conf was set, by default, to just "listen 80" with no address. Anyway, thank you, and thanks to the other posters and forum in general for making my apache server work :>