#1
  1. No Profile Picture
    Registered User
    Devshed Newbie (0 - 499 posts)

    Join Date
    Jul 2013
    Posts
    3
    Rep Power
    0

    Os 10048 only one usage of each socket address is permitted.


    Os 10048 only one usage of each socket address is permitted. could not bind to 0.0.0.0:80?
    my apache worked correctly last year on windows vista. I started it again now and I get this error. I added the port 80 into the windows firewall exceptions. I fixed the router and mcafee firewalls for port 80. I even tried port 8080 instead of port 80. I took care of skype not using port 80. nothing helped. Anything else that might cause the problem?
  2. #2
  3. No Profile Picture
    Contributing User
    Devshed Novice (500 - 999 posts)

    Join Date
    Oct 2009
    Location
    Nebraska, USA
    Posts
    862
    Rep Power
    275
    open a command prompt window and run netstat -a and look for any entries using port 80...whether it be "listening" or "established". If you find a listing, then, it means that something else is running on your PC and using that port for communicating.

    If you want to try using port 8080 instead, you will have to edit your apache.conf or httpd.conf file and change the Listen rule from 80 to 8080 then save that file and restart apache server to get it to "take hold".
  4. #3
  5. No Profile Picture
    Registered User
    Devshed Newbie (0 - 499 posts)

    Join Date
    Jul 2013
    Posts
    3
    Rep Power
    0
    Thank you so much for replying. I used netstat command and it says that a process is listening to port 80 and when I go to task manager and check that PID, it belongs to apache!

    I did make the changes in httpd.config using port 8080 and I get the same error and with netstat I also see that apache is using this port. exactly the same as port 80.
  6. #4
  7. No Profile Picture
    Contributing User
    Devshed Novice (500 - 999 posts)

    Join Date
    Oct 2009
    Location
    Nebraska, USA
    Posts
    862
    Rep Power
    275
    OK, then, check in all of your apache *.conf files, including the one for vhosts, and make sure that you only find one Listen rule that points to port 80.
    If you find more than one, comment out the others [except for the one in your httpd.conf or apache.conf file], re-save that file.
    Then, restart apache and see if you still get that socket error.
  8. #5
  9. No Profile Picture
    Registered User
    Devshed Newbie (0 - 499 posts)

    Join Date
    Jul 2013
    Posts
    3
    Rep Power
    0
    Thank you again. There was only one Listen command in httpd.conf. I couldn't find any vhost.conf file to check it.
    However, I used my public IP address and a simple php program to check if apache works and I had no problem. I need to ask the client to check, maybe he can access my computer even though I get that socket error message. I will update you and thank you again.
  10. #6
  11. No Profile Picture
    Contributing User
    Devshed Novice (500 - 999 posts)

    Join Date
    Oct 2009
    Location
    Nebraska, USA
    Posts
    862
    Rep Power
    275
    I just re-read your initial post again, and it sounds like the error is from the usage of 0.0.0.0 as part of the Listen rule.

    Try just using Listen 80 instead of Listen 0.0.0.0:80 in your .conf file (assuming you are actually using 0.0.0.0:80) and see if the error goes away [after re-saving and restarting apache].

IMN logo majestic logo threadwatch logo seochat tools logo