Error when trying to start Apache: make_sock bind address

Discussion in 'Apache' started by Lang14, Dec 9, 2008.

  1. #1
    Hello,

    I'm having some issues with starting Apache - I am running Windows XP SP2

    I am receiving this error:
    
    C:\xampp\apache\bin>httpd.exe -k start
    (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
    
    Code (markup):
    I searched all the files for '0.0.0.0:443' but was unable to find it... don't know what's going on.

    Can anyone shed some light?

    Thanks,
    Lang14
     
    Lang14, Dec 9, 2008 IP
  2. HSH

    HSH Peon

    Messages:
    73
    Likes Received:
    2
    Best Answers:
    0
    Trophy Points:
    0
    #2
    Port 443 is for https. Are you running a secure server?
    Did you check the httpd.conf file for the Listen directive? You may already be defining port 443 somewhere else in the file. You could also try applying the Listen directive to only bind to a specific IP address.
     
    HSH, Dec 9, 2008 IP
  3. Lang14

    Lang14 Peon

    Messages:
    2
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #3
    I'm not trying to run a secure server. Is it possible to turn this off?

    Its just a personal web server where I can play with PHP. What will binding it to a specific address do?

    I had the server working before on port 15000 - (80 was being used) so I have

    Listen 15000

    in the httpd.conf file - but its still trying to boot at port 80...
     
    Lang14, Dec 9, 2008 IP
  4. night_fall

    night_fall Peon

    Messages:
    70
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #4
    First verify that you have the ssl_suport in conf set at off

    Second look at your ip addr (ipconfig /all) and listen on this ip address instead of listening on any interface ( 0.0.0.0 ) second verify that the port youo are using is not assigned ( netstat -an) cause the error say exactly that your are trying to use an already asigned port address on the specified interface.
     
    night_fall, Dec 9, 2008 IP