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 revisionLast revisionBoth sides next revision | ||
| nginx_emerg_bind_80_failed_98_address_already_use [2020/06/16 22:43] – [This fixed the problem that Nginx would not start or reload] 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 6: | Line 6: | ||
| Author: rgrz | 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/ |
| - | < | + | I killed everything running on port 80… |
| < | < | ||
| 80/tcp: 3488 3489 3490 </ | 80/tcp: 3488 3489 3490 </ | ||
| - | < | + | after that nginx started normally… |
| ==== The answer was provided by rgrz on February 2018 at the following source: ==== | ==== The answer was provided by rgrz on February 2018 at the following source: ==== | ||
| Line 19: | Line 19: | ||
| [[https:// | [[https:// | ||
| - | ==== To Restart | + | ==== To Start Nginx ==== |
| < | < | ||
| Line 26: | Line 26: | ||
| ==== To Check the Status of Nginx ==== | ==== To Check the Status of Nginx ==== | ||
| - | < | + | < |
| + | |||
| + | ==== To Check the Status of Nginx after changes are made to nginx block files (.conf files) and before a Reload of Nginx ==== | ||
| + | |||
| + | < | ||
| + | |||
| + | You should see something like this after running -- | ||
| + | |||
| + | < | ||
| + | |||
| + | nginx: configuration file / | ||
nginx_emerg_bind_80_failed_98_address_already_use.txt · Last modified: 2020/06/17 17:33 by wikiadmin