Starting apache fails (could not bind to address 0.0.0.0:80)

make_sock: could not bind to address 0.0.0.0:80 windows
permission denied: ah00072: make_sock: could not bind to address
make_sock: could not bind to address [::]:80 mac
make_sock: could not bind to address no listening sockets available, shutting down
apache 2.4 could not bind to address
apache not binding to port
apache unable to bind to port 80
apache could not bind to address selinux

Update: Already fixed, it seems that one of VirtualHosts configurations files was wrong in sites-enabled.

I have Ubuntu 11.10

When I run the command to start apache2:

sudo /etc/init.d/apache2 start

I get the following error message:

Starting web server apache2 apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 for ServerName (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80 no listening sockets available, shutting down Unable to open logs Action 'start' failed.

I run this command in order to get the process that is using the port 80:

sudo netstat -ltnp | grep ':80'

Which returns this output:

tcp6       0      0 :::80                   :::*                    LISTEN      1176/

To know which process is I run this command:

ps -wlp1176

That returns:

F S   UID   PID  PPID  C PRI  NI ADDR SZ WCHAN  TTY          TIME CMD
5 D    33  1176     1  0  80   0 -     0 exit   ?        00:00:00 apache2

But if I try to kill the process:

sudo kill -9 1176

It doesn't kill it, if I run again the netstat command still appears listening and apache start fails.

Any suggestions?

Worked for me running this command:

fuser -k -n tcp 80

Apache: Could not bind address to port (make_sock), Apache: Could not bind address to port (make_sock) sudo /etc/init.d/apache2 start * Starting web server apache2 (98)Address already in use: 0.0.0.0:8080 no listening sockets available, shutting down Unable to open logs fail! 0.0.0.0​:* LISTEN 29004/apache2 tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN  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.

It may be skype or nginx using the port 80.

Try shutting down skype, or running: sudo /etc/init.d/nginx stop

CouldNotBindToAddress - HTTPD, make_sock: could not bind to address 0.0.0.0:80 no listening sockets IP and port not present on the host system, apache httpd will fail to start. There is a port conflict preventing the Apache service from starting. : make_sock: could not bind to address 0.0.0.0:80 The Task Manager and the netstat command both show that the System process with PID 4 is using port 80.

I had the same error, and just want to confirm that running

    sudo netstat -ltnp | grep ':80'

helped me indicate that Hiawatha webserver was in the way of Apache2.

Removing Hiawatha fixed the issue (sudo dpkg --purge hiawatha). Ubuntu 12.04.2 server.

"could not bind to address 0.0.0.0:80 " -- Apache Error, If it can't bind to port 80, chances are you also have IIS running, and more than likely, if you're running Vista or 7, IIS's kernel component that keeps hold of port  Apache Lounge is not sponsored. could not bind to address 0.0.0.0:80 problem: Hi, I encounter a very strange problem when I start apache server.

I had the same problem

For me, apache was already running but it was running the wrong way.

Killing processes didnt work because a daemon kept reinstantiating it.

apachectl stop   

resolved the issue.

12.04, Then a service apache2 start worked fine, and Apache started properly in use: make_sock: could not bind to address 0.0.0.0:80 no listening  C:\Apache24>httpd. (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. (OS 10013)An attempt was made to access a socket in a way forbidden by its access permissions.

Try this, it works for me…

sudo netstat -ltnp | grep ':80'

This would return the following:

tcp6 0 0 :::80 :::* LISTEN 1047/apache2

Then

sudo kill -9 1047

Then I was able to restart Apache and everything was working fine.

Unable to start apache on Plesk for Linux: (98)Address already in , Apache start from the bash fails with the following error: Note: Port (98)Address already in use: make_sock: could not bind to address [::]:443 Starting web server apache2. apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 for ServerName (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80 no listening sockets available, shutting down Unable to open logs Action 'start' failed.

Unable to start Apache: Duplicated Listen entries in Apache , Applicable to: Plesk for Linux Symptoms Unable to start the Apache service in use: AH00072: make_sock: could not bind to address 0.0.0.0:80 the Apache configuration for domains, the process fails with the error below:. (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80 no listening sockets available, shutting down I have the same problem on another DirectAdmin server, but on that server stops apache in one time in the 2 weeks.

Apache httpd fails to start resulting in "Address already in use , to start the Apache httpd service using IBM Cloud Orchestrator fails resulting in the error "Address already in use: make_sock: could not bind  Starting httpd/ web server apache2 : (98)Address already in use: make_sock: could not bind to address [::]:80. (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80. no listening sockets available, shutting down. Unable to open logs.

Could not bind to address 0.0.0.0:443 - Server Config, Starting web server apache2 (98)Address already in use: make_sock: could not bind no listening sockets available, shutting down Unable to open logs fail! Apache binds to *:80, and then tries to also bind on 1.2.3.4:80, which fails because it is already bound by the first line. If you're binding on *:PORT, you do not need to also bind on a specific IP. Trying to listen an IP not bound to an active interface on the server

Comments
  • So what is pid 1176? (ps -wlp1176)
  • 5 D 33 1176 1 0 80 0 - 0 exit ? 00:00:00 apache2
  • So, does that suggest anything to you offhand? Hint: compare to what you're trying to start.
  • It seems to me apache it's already running, but it doesn't serve pages, it doesn't stop and it doesn't start or restart.
  • I just had a similar situation. apache2 process with a pid 1345 was taking the port 80 but did not respond to anything. kill 1345 killed that process and then I could start a new apache2 process.
  • Worked for me too in Debian 4.0.4.
  • I got this error every time restarting instance. do you know how to solve it completely?
  • For people not having problem with the port bind and getting a vhost syntax error, the first you have to do is look for Listen values. Look at wiki.apache.org/httpd/CouldNotBindToAddress at Conflicting Listen directives section
  • This answer needs an explanation of WHY it works to be truly useful.