Apache Server Socket Error
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and apache socket timeout policies of this site About Us Learn more about Stack Overflow the apache socket already in use company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags apache could not bind to address 0.0.0.0 80 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
Apache Could Not Bind To Address 0.0.0.0 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 is only one usage of each socket address apache 443 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 instead. &
Server to listen on specific addresses and make_sock could not bind to address 0.0.0.0.80 windows ports. Overview Special IPv6 Considerations Specifying the protocol with Listen
Ah00451: No Listening Sockets Available, Shutting Down
How This Works With Virtual Hosts See alsoVirtual HostsDNS IssuesComments Overview Related ModulesRelated Directivescore href="./mod/mpm_common.html">mpm_commonOs 10048 Apache Error Windows 7
contribution towards the costs, the time and effort that's going in this site and building. Thank You! Steffen Apache Lounge is not sponsored by anyone.Your https://www.apachelounge.com/viewtopic.php?t=767 donations will help to keep this site alive and well, and continuing https://www.sitepoint.com/unblock-port-80-on-windows-run-apache/ the building of the binaries. Make_sock could not bind to address Goto page 1, 2Next Apache Forum Index -> Hardware & Networking View previous topic :: View next topic Author Message MungbeansJoined: 11 Aug 2006Posts: 10Location: Sydney, Australia Posted: Sat 02 Sep '06 6:56 Post subject: Make_sock could not could not bind to address In the last few days my Apache server on my development machine is not starting up. I get the error message: Code:
Web Dev @ Microsoft SEO By WooRank Books Courses Screencasts Newsletters Versioning Shop Forums Advertise Contribute Contact Us Our Story 995kSubscribers 132kFollowers 80kFollowers Programming Article How to Solve Port 80 Problems When Running Apache on Windows By Craig Buckler October 11, 2011 This article was written in 2011 and remains one of our most popular posts. If you're keen to learn more about using Apache, you may find this more recent article on launching a VM with Apache CloudStack of great interest. If only clients realized the hassles developers encounter with their OS. Clients will call you the second their email fails (they forgot to switch on their router) or their website breaks (they're using IE5.0). Who can you call when Apache won't start because port 80 is blocked? Apologies for not writing a typical web development post but this is exactly the problem I encountered and it seems many others have too. I run Apache and IIS on Windows and prefer a server switching method so only one application listens on port 80 at any time. It works well and I've run similar set-ups on Windows 7, Vista, XP, and NT for many years. Today, however, Apache wouldn't start. The following error appeared in the Application Event Viewer (Administrative Tools): The Apache service named reported the following error: >>> (OS 10013) An attempt was made to access a socket in a way forbidden by its access permissions. :make_sock: could not bind to address 0.0.0.0:80. Another application was hogging port 80. The Obvious Candidates There are a number of well-known Windows programs which use port 80: IIS The most likely culprit is Microsoft Internet Information Server. You can stop the service from the command line on Windows 7/Vista: net stop was /y or XP: net stop