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. 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.Īnother application was hogging port 80. It works well and I’ve run similar set-ups on Windows 7, Vista, XP, and NT for many years.
I run Apache and IIS on Windows and prefer a so only one application listens on port 80 at any time. 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. 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). If only clients realized the hassles developers encounter with their OS. If you’re keen to learn more about using Apache, you may find this of great interest. This article was written in 2011 and remains one of our most popular posts.