Report this

What is the reason for this report?

(98)Address already in use: AH00072: make_sock: could not bind to address [::]:80 - error

Posted on February 10, 2015

Hello,

Being a novice on configuring Apache servers I managed to get my droplet up and running and have two domains pointing to it. Made my own virtual host files using the given tutorials, DNS all figured out…great! It worked all just fine.

But now I cannot reach my two domain anymore and when I restart Apache using terminal (sudo service apache2 restart) I get this error:

  • Restarting web server apache2 AH00548: NameVirtualHost has no effect and will be removed in the next release /etc/apache2/sites-enabled/huizenmeteenverhaal.nl.conf:5 (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80 (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80

I googled a fair bit but got lost in all these different solutions that make my novice head spin.

Any help on this…?

Just can’t get my head around the fact that it was al working just fine, and just stopped.



This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

I am running FreeBSD (Linux like…) without NGINX and had this same problem. It appears that there was a httpd process that was hung. Apparently, this happens every so often. I listed all processes and grep out the httpd process to see what was hung. If you do not manually kill the process, it should timeout eventually. The eventual timeout is probably why the problem fixed itself in some of the previous comments. In my situation, I went ahead and manually killed the process and then started apache. Here’s the commands:

== Notice the commands might vary slightly for Linux ==

= Show processes hung = ps wax | grep httpd

= Kill Process ID 1234 = kill 1234

= Start Apache24 = apachectl start

= Verify it is running = service apache24 status

======

I hope this helps.

For me it was NextCloud causing the issue. I installed it using snap so to remove i just did:

sudo snap remove nextcloud

And apache started right up.

Thanks for all the suggestions!

Also, you can see what processes are using the port by doing:

sudo netstat -peanut | grep ":80"

That may give you a better idea of what’s causing the problem.

I had the same ssue. The problem is that server is being used by nginx! U have to unistall it first

sudo apt-get remove nginx nginx-common # Removes all but config files.

sudo apt-get purge nginx nginx-common # Removes everything

sudo apt-get autoremove #After using any of the above commands, use this in order to remove dependencies used by nginx which are no longer required.

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.