Overview
This tutorial will teach you how to resolve the following Apache error during startup. An attempt was made to access a socket in a way forbidden by its access permissions. : AH00072: make_sock: could not bind to address [::]:80
80 is the standard default port that is used for HTTP communication by the Apache Server. In this scenario you want the Apache server to run on this port.
Error Trace
(OS 10013)An attempt was made to access a socket in a way forbidden by its access permissions. : AH00072: make_sock: could not bind to address [::]:80
Fix
The error is because of port conflict. The Apache is trying to start on port 80, however the port 80 is being used or blocked by another application or server. When two or more applications are trying to use the same port its called as port conflict.
Check the process that is using the port 80.
/> netstat -qo
In this case the IIS server is running on port 80. This could be the most possible case but not always true. The first intelligent guess is the standard servers that run on port 80!
Try to find the process with the process ID.
/> tasklist
tasklist is the command line tool to display the processes and the associated IDs. This command is equivalent to ps utility in Linux.
Alternatively, try accessing the webpage to know the application. We can omit the port number 80 as it is the default port
http://localhost:80
Decide which process should be running on port 80. Change the default port for the IIS server or stop the server.
Start and run the Apache server to resolve the port conflict error.
That’s it!
Related Links
https://www.testingdocs.com/questions/how-to-change-jenkins-port-number-on-windows/
More information on Apache HTTP web server: