By Menj
sudo systemctl status nginx.service
● nginx.service - A high performance web server and a reverse proxy server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2018-03-20 12:36:44 UTC; 3min 24s ago
Process: 27569 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; (code=exited, status=1/FAILURE)
Process: 27565 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=0/SUCCESS)
Mar 20 12:36:43 toyina nginx[27569]: nginx: [emerg] listen() to 0.0.0.0:80, backlog 511 failed (98: Address already in use)
Mar 20 12:36:43 toyina nginx[27569]: nginx: [emerg] listen() to [::]:80, backlog 511 failed (98: Address already in use)
Mar 20 12:36:43 toyina nginx[27569]: nginx: [emerg] listen() to 0.0.0.0:80, backlog 511 failed (98: Address already in use)
Mar 20 12:36:43 toyina nginx[27569]: nginx: [emerg] listen() to [::]:80, backlog 511 failed (98: Address already in use)
Mar 20 12:36:44 toyina nginx[27569]: nginx: [emerg] still could not bind()
Mar 20 12:36:44 toyina systemd[1]: nginx.service: Control process exited, code=exited status=1
Mar 20 12:36:44 toyina systemd[1]: Failed to start A high performance web server and a reverse proxy server.
Mar 20 12:36:44 toyina systemd[1]: nginx.service: Unit entered failed state.
Mar 20 12:36:44 toyina systemd[1]: nginx.service: Failed with result 'exit-code'.
Mar 20 12:39:11 toyina systemd[1]: nginx.service: Unit cannot be reloaded because it is inactive.
Hi anyone would like to help me with this error?
I tried to install an SSL (Lets Encrypt) from this tutorial but after several steps I received this error. I hope someone can point me out on how to solve this.
Thanks!
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Hi,
listen() to 0.0.0.0:80, backlog 511 failed (98: Address already in use)
Nginx is unable to bind to port 80 because another process is already using it. Find out what it is using this command:
sudo netstat -plutn | grep :80
It could be an nginx process that didn’t exit gracefully and is still holding the port.
The issue here is that another process besides nginx is also listening on port 80. Perhaps Apache web server or any other web server. So you can only have one process per port. Hope this helps!
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.