Differences

This shows you the differences between two versions of the page.

--- nginx_emerg_bind_80_failed_98_address_already_use [2020/06/16 22:36] – [This fixed my problem] wikiadmin
+++ nginx_emerg_bind_80_failed_98_address_already_use [2020/06/17 17:32] – [To Check the Status of Nginx and changed .conf before running Reload] wikiadmin
@@ Line 4: / Line 4: @@
 ===== This fixed the problem that Nginx would not start or reload =====
-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?
+Author: rgrz
-I killed everything running on port 80…
+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?
-$ sudo fuser -k 80/tcp
+I killed everything running on port 80…
-/tcp: 3488 3489 3490
+<code>$ sudo fuser -k 80/tcp
+/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 after changes are made to nginx block files (.conf files) and before 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>