nginx_emerg_bind_80_failed_98_address_already_use
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
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:33] (current) – [To Check the Status of Nginx after changes are made to nginx block files (.conf files) and before a Reload of Nginx] wikiadmin | ||
---|---|---|---|
Line 4: | Line 4: | ||
===== This fixed the problem that Nginx would not start or reload ===== | ===== 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/ | + | 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.conf after making changes to nginx webserver blocks (*.conf files) and before performing a reload of Nginx ==== | ||
+ | |||
+ | < | ||
+ | |||
+ | You should see something like this after running -- | ||
+ | |||
+ | < | ||
+ | |||
+ | nginx: configuration file / | ||
+ |
nginx_emerg_bind_80_failed_98_address_already_use.1592346993.txt.gz · Last modified: 2020/06/16 22:36 by wikiadmin