Software⏱️ 2 min read📅 2026-06-02

How to Fix: nginx - nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)

Fix nginx - nginx: [emerg] bind() to [::]:80 failed (9. Check if another process is using port 8. Step-by-step guide included.

Quick Answer: Check if another process is using port 80 and try to restart nginx with the -s reload option instead of -s stop.

📋 Table of Contents

  1. 🛑 Root Causes of the Error
  2. 🛠️ Step-by-Step Verified Fixes
  3. 💡 Conclusion

All of a sudden, you're getting the below nginx error: nginx: [emerg] bind() to [::]:80 failed (98: Address already in use). This occurs when another process is using port 80 and prevents nginx from starting.

🛑 Root Causes of the Error

  • Another process is using port 80.

🛠️ Step-by-Step Verified Fixes

Method 1: Checking and Stopping Other Processes Using Port 80

  1. Step 1: Use the netstat -tlnp | grep 80 command to identify which process is using port 80.

Method 2: Stopping and Restarting Nginx

  1. Step 1: Stop the current nginx process by running sudo service nginx stop (or netstop on Windows).

Method 3: Using Systemd to Manage Nginx

  1. Step 1: Use the sudo systemctl stop nginx command (on Linux) or netstop (on Windows).

💡 Conclusion

By identifying and stopping the process using port 80, you should be able to resolve the error and get your nginx server up and running again.

Did this fix your problem?

If not, try searching for specific error codes.

🔍 Search Error Database

❓ Frequently Asked Questions

🛠️ Related Fixes

How to Fix: Pc crashes shortly after launching game (rainbow

Fix Pc crashes shortly after launching game (rainbow six siege). Compl

How to Fix: Installing an APK on a locked down phone

Installing an APK on a locked down phone: Try using a rooted device, e

How to Fix: New PC build- no signal and no clue

Fix New PC build- no signal and no clue. Complete troubleshooting guid