[thewulf]

Hi Guys,

I have problems starting an Apache server on an german Win XP Home OS.
Following message is shown then in an batch-window:

============================================
Apache 2 is starting ...
(OS 10048)Normalerweise darf jede Socketadresse (Protokoll, Netzwerkadresse oder Anschluss) nur jeweils einmal verwendet werden.
: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
=============================================

For englishmen, the 2nd+3rd lines mean:
Normaly each socketadress (protocoll,
networkadress or port) may be only used one time.

What can I do to fix this problem?
Thank you for helping me!

TheWulf
(you can contact me at: thedarkwulf99@gmx.net)

[dianeghir]

Hi

I am having the same problem starting Apache on my Windows 2000 Pro machine. (see error below)

Did you ever figure out how to start Apache?

thanks

diane

************************************************
C:\xampp>apache_start.bat
Diese Eingabeforderung nicht waehrend des Running beenden
Bitte erst bei einem gewollten Shutdown schliessen
Please close this command only for Shutdown
Apache 2 is starting ...
(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:443
no listening sockets available, shutting down
Unable to open logs
*************************************************

Originally Posted by thewulf

Hi Guys,

I have problems starting an Apache server on an german Win XP Home OS.
Following message is shown then in an batch-window:

============================================
Apache 2 is starting ...
(OS 10048)Normalerweise darf jede Socketadresse (Protokoll, Netzwerkadresse oder Anschluss) nur jeweils einmal verwendet werden.
: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
=============================================

For englishmen, the 2nd+3rd lines mean:
Normaly each socketadress (protocoll,
networkadress or port) may be only used one time.

What can I do to fix this problem?
Thank you for helping me!

TheWulf
(you can contact me at: thedarkwulf99@gmx.net)

[newiaqua]

Hello, I think that this Apache error message is produced because you are having firewall or somethink like. You can either remove or adjust your firewall accordingly or search for Windows's network firewall settings. There must be something about port bidings.

Other solution is to make Apache listen not to 80 but to 3128 port(ports < 1024 are more often used for system service bindings).

Third solution is to change binging address:
in your httpd.conf write this:
Listen 127.0.0.1:80
instead of:
Listen 0.0.0.0:80

Personally I am using Knoppix and there are no such problems.
Hope It helps...

[abdu5hahid]

I was having same issue with Apache2 on Windows, and I tried disabling my firewall and changing binding to specific IP address instead of all unassigned (0.0.0.0).

Issue still persisted even though Apache2/Tomcat had worked previously on my system. Noticed that when I was reinstalling was defaulting to 443 as main port and I left as is before thinking it understood that to be SSL.

Think it was trying to use 443 as the default port, so it was coliding with 443 being SSL port; hence message about only one binding at a time.

When I changed HTTPD.conf to 80 it worked fine with SSL and http.

[maurito]

Originally Posted by abdu5hahid

I was having same issue with Apache2 on Windows, and I tried disabling my firewall and changing binding to specific IP address instead of all unassigned (0.0.0.0).

Issue still persisted even though Apache2/Tomcat had worked previously on my system. Noticed that when I was reinstalling was defaulting to 443 as main port and I left as is before thinking it understood that to be SSL.

Think it was trying to use 443 as the default port, so it was coliding with 443 being SSL port; hence message about only one binding at a time.

When I changed HTTPD.conf to 80 it worked fine with SSL and http.

I've had the same problem. I noticed that when i reboot my computer (running XP pro), sometimes Apache worked. Then, i change the port to 3128 and it worked. But, then I was illuminated by God, and do a netstat -ao (-o displays the PID) and discover that Skype was listening in port 80 instead of apache -that is, i have both set up to run at startup, thus, if apache started first, it will have por 80 available, and skype not, and vice-versa-. So my solution was to remove skype from startup -i don't use it too often- and make apache (and myself) happy by making port 80 available.
Sorry about my english, ajejaej I'm from Argentina..

[bizzar528]

uninstall IIS

[Fletch]

I had the same problem, so i don't use apache under the Windows.

[iga3k]

as maurito said, skype could be the problem, and athor programs that listen on port 80. So, by a netsetat -ao you can see all connections on local machie, and you can identify by PID the process that is listening on port 80.

If skype is the one, there is an option in connection tab in skype that says Use port 80 and 443 as alternatives for incoming connections ...uncheck it

[hightechguy]

Hi, guys

I have pretty much the same problem - Apache 2.2 stopped running after XP SP3 installation.

httpd.exe -k start gives

(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:80
no listening sockets available, shutting down
Unable to open logs

netstat -ao gives no information on port 80, looks like port 80 is free

I've tried to :

* Make Apache to Listen 127.0.0.1:80 as newiaqua adviced - no luck
* modify Apache port number to 3128 as newiaqua adviced - no luck
* turned off my Windows XP firewall - no luck
* uncheck Skype port 80 usage, like iga3k and maurito said - no luck
* reinstall Apache- no luck

Any ideas are highly appreciated

Thank you in advance,
hightechguy

[mab]

This problem is caused by another service listening to TCP/IP port 80.

I don't use Skype, but after you change what port it is configured to use, you probably need to restart it and/or reboot your computer to get the change to take effect.

You would need to post infomation about how you were changing the Apache port number and if you stoped and started Apache to get any changes made to take effect.

If you are still having this problem, there could be a second service listening to on port 80.