Apache - Could not Bind to Address 0.0.0.0:443 menu

User Tag List

Results 1 to 2 of 2
  1. #1
    thenewchilledwow's Avatar Private
    Reputation
    1
    Join Date
    Jun 2010
    Posts
    5
    Thanks G/R
    0/0
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Apache - Could not Bind to Address 0.0.0.0:443

    Please help me with this issue. Last night my server was running perfectly fine, but when I turn it on today, Apache won't run.

    I get this:


    only one usage of each socket address (protocol/network address/port) is normally permitted. :make_sock: could not bind address 0.0.0.0:443
    no listening sockets available, shutting down
    Unable to open logs

    Apache konnte nicht gestarter werden
    Apache could not be started
    Press any key to continue . . .


    I turned off Skype and ended its process , so what's the matter? And yes I've tried restarting comp.

    I'm currently using ArcEmu 3.3.3 (TreeTree's repack). Yes I know, Arc is buggy as shit and repacks fail but, it worked last night. :/
    Last edited by Ground Zero; 06-17-2010 at 04:40 AM.

    Apache - Could not Bind to Address 0.0.0.0:443
  2. #2
    Exnintythree's Avatar Active Member
    Reputation
    25
    Join Date
    Aug 2008
    Posts
    59
    Thanks G/R
    0/0
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    It seems your Apache is trying to run on Port 443?

    Go to command prompt and type netstat -aon
    A large list of ports will come up, scroll until you see "0.0.0.0:443"



    Now look at the far right of the "0.0.0.0:443" there should be a number. This is the (PID) Process ID of the program that's using the port, causing Apache not to work. Since only one program can be on a port at a time, you must disable it so Apache can use it.




    To do this, go into Task Manager (Hold: Ctrl+Alt+Del). Once Task Manager comes up, look for the "Processes" tab at the top. Click it.

    Picture:


    You should see a list, now look for the program with the same process ID (PID) as shown in the command prompt. If your task manager doesn't show process ID (PID) , then click "View" at the top of the Task Manager, and click "Select Columns" on the check-box list, find PID, and check it, then click "OK"

    Picture:




    Now that your Task Manager shows PID, find the program with the same PID as shown in the command prompt, click it, then click "End Process" (make sure it's not an important program first!!) now that the program isn't using that port up, your apache server should start up normally!

    Here's a quick picture: (These Numbers should be the same.)




    **Notice how Apache is running on Task Manager as process 4044, and on command prompt as "0.0.0.0:443" "4044" But on your Task Manager, another program besides Apache may be running.
    Last edited by Exnintythree; 06-27-2010 at 10:43 AM.
    Honorbuddy staff.

Similar Threads

  1. The memory could not be "read".
    By naa in forum WoW Memory Editing
    Replies: 6
    Last Post: 02-22-2016, 04:06 AM
  2. [Core] Logon Server Ports 8093 and 3724 not binding?
    By Wintchman11 in forum WoW EMU Questions & Requests
    Replies: 3
    Last Post: 07-09-2010, 04:03 PM
  3. [ArcEmu] Could not open configs/logon.conf / Config file could not be rehashed
    By Renas in forum WoW EMU Questions & Requests
    Replies: 1
    Last Post: 05-16-2010, 11:29 PM
  4. can not bind to carolineserver.co.nr:8085
    By JF1985 in forum WoW EMU Questions & Requests
    Replies: 3
    Last Post: 10-30-2009, 10:24 AM
All times are GMT -5. The time now is 07:16 PM. Powered by vBulletin® Version 4.2.3
Copyright © 2024 vBulletin Solutions, Inc. All rights reserved. User Alert System provided by Advanced User Tagging (Pro) - vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.
Digital Point modules: Sphinx-based search