Nginx 502 Bad Gateway

[Hentai]

@julian Yes, I have restart it, using sudo service nginx restart

[julian]

Does the huoshaolin file have permissions that are readable by the nginx user?

[Hentai]

@julian I was created this file as root user...

[julian]

@Hentai Run ls -l and inspect the permissions. There needs to be an r in the third-last character:

 ~ $ ls -l /etc/nginx/sites-available/localhost-nodebb 
-rw-r--r-- 1 root root 515 Mar 13 16:14 /etc/nginx/sites-available/localhost-nodebb

[Hentai]

@julian

[julian]

Then I am officially out of ideas

[Hentai]

@julian

I was following this guide to install my Nginx:

But I didn't use a regular, non-root user to install it (I installed it using root user), maybe this is the problem ?

[julian]

No, that shouldn't be a problem. The 502 error usually means a connection to the backend server could not be reached...

Either because no server block matched, or because the NodeBB process could not be proxied to...

Are you running NodeBB as root? I can't imagine that would break anything though...

[Hentai]

@julian Yeah, I was start NodeBB in root:

[Guiri]

Your nginx.conf matches mine. Can you post sudo tail /var/log/nginx/error.log?

[Hentai]

@Guiri Of course:

2014/07/09 01:13:17 [error] 8494#0: *26 connect() failed (111: Connection refused) while connecting to upstream, client: 113.109.53.7, server: huoshaolin.com, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:4567/", host: "huoshaolin.com"
2014/07/09 01:13:17 [error] 8494#0: *26 connect() failed (111: Connection refused) while connecting to upstream, client: 113.109.53.7, server: huoshaolin.com, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:4567/favicon.ico", host: "huoshaolin.com"
2014/07/09 01:17:47 [error] 8494#0: *31 connect() failed (111: Connection refused) while connecting to upstream, client: 113.109.53.7, server: huoshaolin.com, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:4567/", host: "www.huoshaolin.com"
2014/07/09 01:17:47 [error] 8494#0: *31 connect() failed (111: Connection refused) while connecting to upstream, client: 113.109.53.7, server: huoshaolin.com, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:4567/favicon.ico", host: "www.huoshaolin.com"
2014/07/09 01:17:50 [error] 8494#0: *31 connect() failed (111: Connection refused) while connecting to upstream, client: 113.109.53.7, server: huoshaolin.com, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:4567/", host: "www.huoshaolin.com"
2014/07/09 01:17:50 [error] 8494#0: *31 connect() failed (111: Connection refused) while connecting to upstream, client: 113.109.53.7, server: huoshaolin.com, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:4567/favicon.ico", host: "www.huoshaolin.com"
2014/07/09 01:17:52 [error] 8494#0: *31 connect() failed (111: Connection refused) while connecting to upstream, client: 113.109.53.7, server: huoshaolin.com, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:4567/", host: "www.huoshaolin.com"
2014/07/09 01:17:53 [error] 8494#0: *31 connect() failed (111: Connection refused) while connecting to upstream, client: 113.109.53.7, server: huoshaolin.com, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:4567/favicon.ico", host: "www.huoshaolin.com"
2014/07/09 01:26:43 [error] 8494#0: *38 connect() failed (111: Connection refused) while connecting to upstream, client: 107.178.200.63, server: huoshaolin.com, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:4567/", host: "www.huoshaolin.com"
2014/07/09 01:26:45 [error] 8494#0: *40 connect() failed (111: Connection refused) while connecting to upstream, client: 107.178.200.63, server: huoshaolin.com, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:4567/favicon.ico", host: "www.huoshaolin.com"

[Tanner]

@Hentai said:

proxy_pass http://127.0.0.1:4567/;

Try changing this to proxy_pass http://huoshaolin.com:4567/;

[A Former User]

@Tanner said:

@Hentai said:

proxy_pass http://127.0.0.1:4567/;

Try changing this to proxy_pass http://huoshaolin.com:4567/;

I was having the same issue - this fix worked for me.
Just like @Hentai, I did everything as root - and made sure to restart Nginx when appropriate.

[julian]

Heh, I guess I did assume that nginx and NodeBB were on the same server

[Hentai]

@Tanner @Albus

Oh ! it really works !!! Thank you very much

[julian]

Haha @Tanner @Albus, you guys should hang around more often

[Tanner]

@julian I'm around, just trying to figure out my own apache configuration for what it's worth

[Hentai]

@julian Yeah, they were on the same server , and thank you for your warm help

[A Former User]

@Hentai, glad to hear it was resolved.
@julian, they're on the same server, so I have no idea what the issue was. Only variation from the docs was running as root, not just a sudo user.

I'm just now getting to play with the platform in full swing, and it certainly seems promising. It has all the important aspects of a social experience, without the clutter.

I have only a few suggestions, but I hear they drop in 0.5, so I can't wait

[EpicIM_Inc]

Oddly enough this fixed it for me to, hopefully those searching for a** fix to nginx 502 bad gateway with NodeBB** come across this solution as it took me some time. I didn't think it would work because it was on the same server but it did.

proxy_pass http://mydomain.com:4567/;