nginx_emerg_bind_80_failed_98_address_already_use
This is an old revision of the document!
Table of Contents
Nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
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?
I killed everything running on port 80…
$ sudo fuser -k 80/tcp 80/tcp: 3488 3489 3490
after that nginx started normally…
The answer was provided by rgrz on February 2018 at the following source:
To Restart Nginx
sudo systemctl start nginx
To Reload Nginx
sudo systemctl start nginx
To Check the Status of Nginx
sudo systemctl status nginx
nginx_emerg_bind_80_failed_98_address_already_use.1592347269.txt.gz · Last modified: 2020/06/16 22:41 by wikiadmin