nginx not listening to port 80

Question

I\'ve just installed a Ubuntu 12.04 server and nginx 1.2.7, removed default from sites-enabled and added my own file into sites-available and symli

Answer 1

I had faced the same problem over the server, here I am listing the how I had solved it :

Step 1 :: Installing the Ngnix

sudo apt update
sudo apt install nginx

Step 2 – Adjusting the Firewall

sudo ufw app list

You should get a listing of the application profiles:

Output Available applications: Nginx Full Nginx HTTP Nginx HTTPS OpenSSH

As you can see, there are three profiles available for Nginx:

Nginx Full: This profile opens both port 80 (normal, unencrypted web traffic) and port 443 (TLS/SSL encrypted traffic)

Nginx HTTP: This profile opens only port 80 (normal, unencrypted web traffic)

Nginx HTTPS: This profile opens only port 443 (TLS/SSL encrypted traffic)

Since I haven’t configured SSL for our server yet in this guide, we will only need to allow traffic on port 80.You can enable this by typing:

sudo ufw allow 'Nginx HTTP'

You can verify the change by typing:

sudo ufw status

Step 3 – Checking your Web Server

systemctl status nginx

Now Check port 80 , It worked for me hope will work for you as well.

Answer 2

If your logs are silent on the issue, you may not be including the sites-enabled directory. One simple way to tell that the site is being loaded is to set the error/access log path within your server block to a unique path, reload nginx, and check if the files are created.

Ensure the following include directive exists within the http context in /etc/nginx/nginx.conf.

http {
  ...
  include /etc/nginx/sites-enabled/*;
}

Answer 3

While we all think we don't make silly mistakes, we do.

So, if you are looking into NGINX issues and all signs are showing it should work then you should take a step away from the files and look downstream.

System Firewall, Hardware Firewall, Nat router/firewall.

For myself this issue was my router, I run a home lab and so I can access services behind my router from afar I use NGINX to reverse proxy as my router only handles incoming based on IP and doesn't do any handling of hostnames, I'm sure this is all fairly normal.

In any case my issue cropped up as I was securing my network a few days ago, removing some port forwarding that isnt needed any longer and I accidentally removed port 80.

Yes it was as simple as forwarding that port again to NGINX and all was fixed.

I will now walk away with my head hung in extreme shame though I leave this answer to show my gratitude to the people in this thread that lead me to find my own error.

So thank you.

Answer 4

You are probably binding nginx to port 80 twice. Is that your full config file? Don't you have another statement listening to port 80?