nginx_emerg_bind_80_failed_98_address_already_use
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revisionNext revisionBoth sides next revision | ||
nginx_emerg_bind_80_failed_98_address_already_use [2020/06/16 22:35] – created wikiadmin | nginx_emerg_bind_80_failed_98_address_already_use [2020/06/17 17:29] – [To Check the Status of Nginx and changed .conf before running Reload] wikiadmin | ||
---|---|---|---|
Line 2: | Line 2: | ||
====== Nginx: [emerg] bind() to [::]:80 failed (98: Address already in use) ====== | ====== Nginx: [emerg] bind() to [::]:80 failed (98: Address already in use) ====== | ||
- | ===== This fixed my problem ===== | + | ===== This fixed the problem |
- | 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/ | + | Author: rgrz |
- | I killed everything | + | Ok, now this is weird. |
- | $ sudo fuser -k 80/tcp | + | I killed everything running on port 80… |
- | 80/tcp: 3488 3489 3490 | + | |
+ | < | ||
+ | 80/tcp: 3488 3489 3490 </ | ||
after that nginx started normally… | after that nginx started normally… | ||
+ | |||
+ | ==== The answer was provided by rgrz on February 2018 at the following source: ==== | ||
[[https:// | [[https:// | ||
+ | |||
+ | ==== To Start Nginx ==== | ||
+ | < | ||
+ | |||
+ | ==== To Reload Nginx ==== | ||
+ | < | ||
+ | |||
+ | ==== To Check the Status of Nginx ==== | ||
+ | < | ||
+ | |||
+ | ==== To Check the Status of Nginx and changed .conf before running Reload ==== | ||
+ | |||
+ | < | ||
+ | |||
+ | You should see something like this after running -- | ||
+ | |||
+ | nginx: the configuration file / | ||
+ | nginx: configuration file / | ||
+ |
nginx_emerg_bind_80_failed_98_address_already_use.txt · Last modified: 2020/06/17 17:33 by wikiadmin