Apache Server Os 10048 Error
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings
Apache Could Not Bind To Address 0.0.0.0 80
and policies of this site About Us Learn more about Stack Overflow apache could not bind to address 0.0.0.0 443 the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags make_sock could not bind to address 0.0.0.0.80 windows Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only
Only One Usage Of Each Socket Address Apache 443
takes a minute: Sign up Apache webserver error on startup [closed] up vote 15 down vote favorite 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. : make_sock: could not bind to address 0.0.0.0:443 no listening sockets available, shutting down Unable to open logs That
Os 10048 Apache Error Windows 7
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 19k63156 asked Feb 11 '12 at 15:35 Mackintoast 4174822 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
I start Apache, I get the error message: Only one usage of each socket address (protocol/network address/port) is normally permitted. :make_sock: ah00451: no listening sockets available, shutting down could not bind to address 0.0.0.:80 Unable to open logs. I think it
Only One Usage Of Each Socket Address Is Normally Permitted Apache
means something else on my machine is using port 80. 1) How do I find out what else is using the apache service named reported the following error unable to open logs port 80? 2) I found something about a conflict with Apache & IIS (Internet Information Service) webserver but don't know anything about IIS . > How do I check to see if http://stackoverflow.com/questions/9241409/apache-webserver-error-on-startup I have that on my PC? > If it's on my PC how do I disable it? 2) Is there another port I can use for Apache? If so, > What other ports are available? > Do I only have to change the port number in the 'Servername=' parameter in the Configuration file? I'd appreciate assistance on this so I can proceed with learning http://www.ozzu.com/mswindows-forum/apache-error-cound-not-bind-address-t31963.html PHP. Thanks! LAbrego brego from LA Posts: 2856 3+ Months Ago Hi, Chuck, Welcome to Ozzu. I don't use Apache but someone else can help you with that, don't worry, there's a lot of friendly and skilled people here (I am the black sheep ) To stop IIS try this 1- Goto control panel > Administrative Tools > Internet Information Service (IIS) Manager 2- In IIS Manager, right click the local computer, point to All Tasks, then click Restart IIS 3- In the What do you want IIS to do list, select Stop Internet Services on
using apache_start.bat? (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 https://elenaneacsu.wordpress.com/2011/02/18/apache-cannot-start-error-os-10048-about-port-443-80/ available, shutting down Unable to open logs or Only one usage of each http://superuser.com/questions/795132/how-to-determine-why-port-443-is-already-in-use 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 There are several ways to fix this. One option would be to change IIS port bindings, which I will cover in a future post. Another option could not is to change the httpd.conf, under:
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 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 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 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,2072774117 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: