Question

Node.js - Nginx 502 Bad Gateway on POST/PUT

Posted October 25, 2014 24.2k views

Hi,

I have a MEAN app and on localhost works fine.

I have a CentOs droplet with node.js and nginx, but that i make for example a submit form by POST or PUT, console returns “502 Bad Gateway”.

Each time i restart nginx, shows:
nginx: [emerg] unknown directive “proxyhttpversion”

My conf in nginx:

server {
    listen 80;
    server_name mysub.domain.com
    location / {
        proxy_pass http://localhost:3003;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_cache_bypass $http_upgrade;
        proxy_connect_timeout       300;
        proxy_send_timeout          300;
        proxy_read_timeout          300;
        send_timeout                300;
    }
}

My niginx version is 1.0.15

Thanks for now. =D

Add a comment
jefferson
By:
jefferson
Add a comment
1 comment
  • ricardoalves October 26, 2014
    Reply Report

    Usually when shown 502 error is the following:
    Nginx running as proxy for Apache web server.
    Nginx running with PHP-FPM daemon.
    Nginx running with other services as gateway.
    Bad buffering/timeout configuration.

    Are you running Nginx using PHP-FPM?

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
2 answers
vegardx October 25, 2014
[deleted]
Reply Report
  • vegardx October 25, 2014

    Err, that edit thing is really dangerous.

    You probably are running an older version of Nginx that does not support that directive. It was introduced in Nginx 1.1.4.

    Check what version of Nginx you’re running:

    nginx -v
    Reply Report
  • jefferson October 25, 2014

    So…

    I update to Nginx to 1.6.2.

    Dont show more “nginx: [emerg] unknown directive "proxyhttpversion”.

    But the POST/PUT form continue… Same error on console…
    “http://mysub.domain.com/route_to_post/ 502 Bad Gateway - 309ms”

    =/

    Reply Report
  • vegardx October 25, 2014

    Can you post the errors Nginx is throwing? Are you sure the backend is actually up and responding to requests?

    Reply Report
  • jefferson October 25, 2014

    Nginx log from my proxy:

    2014/10/25 15:53:41 [error] 993#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 221.15.24.44, server: mysub.domain.com, request: "POST /contributors HTTP/1.1", upstream: "http://[::1]:3003/users", host: "mysub.domain.com", referrer: "http://mysub.domain.com/users/create"
    Reply Report
  • vegardx October 25, 2014

    Well - it says what is wrong right there. I bet your application is not listening for connections on IPv6.

    Reply Report
  • jefferson October 25, 2014

    No, is no listening on IPv6.

    How i make to Nginx works just with IPv4?

    Reply Report
  • vegardx October 25, 2014

    Since you’re doing proxypass to localhost it will be whatever resolves to localhost in your /etc/hosts-file that makes it bind to that interface. Change out localhost with 127.0.0.1 in your proxypass and you’ll pass it only to 127.0.0.1.

    Reply Report
ryanpq December 21, 2017

This question was answered by @vegardx

Since you’re doing proxypass to localhost it will be whatever resolves to localhost in your /etc/hosts-file that makes it bind to that interface. Change out localhost with 127.0.0.1 in your proxypass and you’ll pass it only to 127.0.0.1.

Reply Report

Looking for something else?

Ask a new question Search for more help