Make_sock Error Apache Windows
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or apache could not bind to address 0.0.0.0 80 posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join apache only one usage of each socket address (protocol/network address/port) is normally permitted the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes
Apache Could Not Bind To Address 0.0.0.0 443
a minute: Sign up Apache webserver error on startup [closed] up vote 16 down vote favorite 1 I just switch to Apache webserver and I receive an error (OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted.
Ah00451: No Listening Sockets Available, Shutting Down
: make_sock: could not bind to address 0.0.0.0:443 no listening sockets available, shutting down Unable to open logs That is what I have got after running httpd from commandline. I reset my apache documentRoot as well as server's listening port to one that is free to use already, I have no idea about this error with port 443, is it something about SSL ? UPDATE I am using XP apache share|improve this question edited Feb 11 '12 at 15:50 Oldskool 19.2k63156 windows could not start apache 2.4 on local computer asked Feb 11 '12 at 15:35 Mackintoast 4224922 closed as too localized by SztupY, Roman C, jeb, Lipis, Charan Mar 11 '13 at 11:23 This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question. 2 You might have better luck asking on serverfault.com –Toby Allen Feb 11 '12 at 15:38 +1 for serverfault migration, belongs there instead. –Oldskool Feb 11 '12 at 15:47 add a comment| 7 Answers 7 active oldest votes up vote 6 down vote accepted Copying and pasting your exact error into google gave a couple of answers. http://www.digitalsanctum.com/2007/08/18/apache-httpd-address-already-in-use-make_sock-could-not-bind-to-address-0000443/ Port 443 seems to already be in use. Possibly by your old server. share|improve this answer answered Feb 11 '12 at 15:43 dm03514 28.9k54874 add a comment| up vote 22 down vote For Windows XP netstat -ano Find the process id that is using port 443, and kill it using task manager For me it was IIS using the port. share|improve this answer answered Aug 1 '12 at 7:31 keith 2,05511928 7 +1, netstat pointed me to the culprit: in my case it was Skype. Had to go
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business
Windows Could Not Start Apache 2.2 On Local Computer
Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation nod32 (add apache to the imon exceptions' list for it to allow apache to bind) Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just apache os 10048 like you, helping each other. Join them; it only takes a minute: Sign up Windows could not start the Apache2 on Local Computer - problem up vote 55 down vote favorite 27 During the installation of Apache2 I http://stackoverflow.com/questions/9241409/apache-webserver-error-on-startup got the following message into cmd window: 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 name , using 192.168.1.3 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:80 no listening sockets available, shutting down Unable http://stackoverflow.com/questions/195641/windows-could-not-start-the-apache2-on-local-computer-problem to open logs Note the errors or messages above, and press the key to exit. 24... and after installing everything look fine, but it isn't. If I try to start service I got the following message: Windows could not start the Apache2 on Local Computer. For more information, review the System Event Log. If this is a non-Micorsoft service, contact the service vendor, and refer to service-specific error code 1. Apach2 version is 2.2.9 Does anyone have the same problem, or could help me. windows windows-xp apache2 share|improve this question asked Oct 12 '08 at 16:13 vaske 3,412103555 add a comment| 18 Answers 18 active oldest votes up vote 126 down vote accepted There is some other program listening on port 80, usual suspects are Skype (Listens on port 80) NOD32 (Add Apache to the IMON exceptions' list for it to allow apache to bind) Some other antivirus (Same as above) Way to correct it is either shutting down the program that's using the port 80 or configure it to use a different port or configure Apache to listen on a different port with the Listen directive in httpd.conf. In the case of antivirus configure the antivirus to allow Apache to bind on the port you have chosen. Way to diagnose which app, if any, has bound to port 80 is run th
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of http://superuser.com/questions/795132/how-to-determine-why-port-443-is-already-in-use this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question could not Anybody can answer The best answers are voted up and rise to the top How to determine why port 443 is already in use? up vote 0 down vote favorite I'm running Apache 2.4.10 on a Windows 7 machine and am trying to add SSL connections. Port 80 connections work fine, and I'm trying to add port 443. When the httpd.conf gets Listen 443 apache could not added it fails to start up: c:\Apache24\bin> httpd.exe -k start (OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted. : AH00072: make_sock: could not bind to address [::]:443 (OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted. : AH00072: make_sock: could not bind to address 0.0.0.0:443 AH00451: no listening sockets available, shutting down AH00015: Unable to open logs A check using netstat at first revealed Chrome using port 443, so I quit Chrome and after the time out elapsed, the ports are now empty using netstat, but the server still fails to start when Listen 443 is present: c:\Apache24\bin> netstat -ano | grep 443 How can I determine who is already on port 443 and blocking the Apache Server from using that port? windows-7 port apache-http-server sockets netstat share|improve this question asked Aug 10 '14 at 21:06 WilliamKF 3,2122774118 add a comment| 3 Answers 3 active oldest votes up vote 4 down vote accepted The issue appears to have been Apache conflicting with itself due to there being two Listen 443 directives, the one I added and one via include: