nginx halp plskthx [solved]

[termnml]

PORT     STATE SERVICE
22/tcp   open  ssh
4567/tcp open  tram

---

1st reason could be your nginx is not running at all.
But you mentioned you restarted so I guess the 2nd possibility.

/etc/init.d/nginx start

---

your firewall is blocking port 80

[kevin]

@termnml said:

your firewall is blocking port 80

nginx is definitely running. It's routing http://BikeNode.com to the same broken page as http://178.62.247.86/ . How do I check to see if my firewall is blocking 80?

[termnml]

@kevin
That your domain is resolved to your IP adress is not the work of nginx. That does the DNS service for you.
The Check depends on your server. If you manage it all your own eg root-server. Check: iptables -L -n
If the output is very long simply do a iptables -L -n | grep :80

If your firewall is set by any software/interface of your provider, you have to look there.

[kevin]

@termnml
ah you're right about dns. I don't think there is a firewall. I'm just using digitalocean. If i run iptables -L -n i get:

Chain INPUT (policy ACCEPT)`
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)`
target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

[a_5mith]

When you run sudo service nginx reload, what do you get? Does it say fail? Or ok?

What's the output of nginx -t

[kevin]

@a_5mith

[email protected]$#!%:~/nodebb# service nginx reload
* Reloading nginx configuration nginx                                   [ OK ] 
[email protected]$#!%:~/nodebb# nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful

[Scuzz]

try changing proxy_pass http://178.62.247.86:4567/; to proxy_pass http:127.0.0.1:4567/;

[kevin]

Ran the following:

[email protected]$#!%:~# cd /etc/nginx/sites-available
[email protected]$#!%:/etc/nginx/sites-available# sudo nano bikenode.com



  GNU nano 2.2.6             File: bikenode.com                                 

server {
    listen       80;
    server_name  bikenode.com;
    location / {
        proxy_pass        http:127.0.0.1:4567/;

        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

        proxy_redirect off;
       proxy_buffering   off;

      proxy_http_version 1.1;
       proxy_set_header Upgrade $http_upgrade;
       proxy_set_header Connection "upgrade"
    }
}

[email protected]$#!%:/etc/nginx/sites-available# service nginx restart
* Restarting nginx nginx                                                [ OK ] 

@Scuzz, Doesn't appear to have made a difference. Cleared browser cache but let me know if it's working for anyone else.

[termnml]

I dont think it has anything to do with the configs.
Otherwise nginx would complaining.
I'm curious that your port 80 isn't visible to the outside at all.

Which system is running?
Debian, Ubuntu, CentOS?

[kevin]

@termnml latest ubuntu. If anyone's interested in peeking around i can send them a userid/pw.

[termnml]

This sir is never a good idee
For such configs is always root needed.
And don't give this access to "some guys" on the internet.

Latest Ubuntu? On a server? For production? O.o arg

[termnml]

Could it be that you started with a LAMP setup and wanted to switch to nginx (because it is so awesome :D)?

[kevin]

I dont believe so. Im terrible with this stuff and was following the nodebb for dummies installation.

[termnml]

@kevin said:

I dont believe so. Im terrible with this stuff and was following the nodebb for dummies installation.

Was Apache installed on your system or nginx already?

[kevin]

I don't think so. just node-v0.10.33 on ubuntu 14.04.
in the meantime i'll start a new droplet and see if I can't get it to work on that.

[termnml]

Could you paste logs for nginx (pastebin)?
pastebin: option Paste Exposure: Unlisted

Try to reach your normal domain and then do:

tail /var/log/nginx/error.log 
tail /var/log/nginx/access.log

[kevin]

http://pastebin.com/dFh3V03B

[wzrdtales]

Seems like NGINX is not listening on Port 80.

Post the result of:

netstat -anp | grep -e ':80'

One question, did you already created the symlink in sites-enabled?

[kevin]

@departman said:

Seems like NGINX is not listening on Port 80.

Post the result of:

netstat -anp | grep -e ':80'

One question, did you already created the symlink in sites-enabled?

 [email protected]:~# netstat -anp | grep -e ':80'
 [email protected]:~# 

nothing?

[wzrdtales]

Yeah nothing, nginx is not listening.

Check if /etc/nginx/sites-enabled/ is empty.

NGINX only do not listen on a port if :

1. Not Running
2. There are no configs that define to listen on port 80