Install Config Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Nginx: [emerg] bind() to [::]:80 failed (98: Address already in use) ======

===== This fixed the problem that Nginx would not start or reload =====

Author: rgrz

Ok, now this is weird. I am pretty sure nginx service was stopped. And I don’t have apache or anything running on the server that could use port 80… Could it have been that nginx left some resource that kept port 80 busy while certbot reconfigured/restarted the server? 

I killed everything running on port 80… 

<code>$ sudo fuser -k 80/tcp
80/tcp: 3488 3489 3490 </code>

after that nginx started normally…

==== The answer was provided by rgrz on February 2018 at the following source: ====

[[https://community.letsencrypt.org/t/nginx-emerg-bind-to-80-failed-98-address-already-in-use/52914/2]]

==== To Start Nginx ====
<code>sudo systemctl start nginx</code>

==== To Reload Nginx ====
<code>sudo systemctl start nginx</code>

==== To Check the Status of Nginx ====
<code>sudo systemctl status nginx.service</code>

==== To Check the Status of Nginx.conf after making changes to nginx webserver blocks (*.conf files) and before performing a reload of Nginx ====

<code>sudo nginx -t</code>

You should see something like this after running --

<QUOTE>nginx: the configuration file /etc/nginx/nginx.conf syntax is ok

nginx: configuration file /etc/nginx/nginx.conf test is successful</QUOTE>