Nginx – CouchDB test suite gives 502 Bad Gateway behind Nginx proxy

couchdbnginxPROXY

I installed CouchDB on my Ubuntu server from the stable PPA. Then I put this in my nginx.conf:

server {
    listen 80;
    server_name couchdb.mydomain.com;

    location / {
        proxy_pass http://127.0.0.1:5984;
    }
}

setting up a subdomain to access Futon. When I go to couchdb.mydomain.com/_utils and run the CouchDB test suite, Nginx gives 502 Bad Gateway errors. Any ideas on what would be causing this? Is it possible to know what url the test suite is trying to go to?

Best Answer

On Firefox, you can use the livehttpheaders addon to watch the headers and try to diagnose your problem.

On Chrome, you can go to chrome://net-internals and do the same on the events tab.

In any case, it seems that test fails behind proxy problem is a known one:

Known Test Suite issue with reverse proxy from subdirectory URL

If the reverse proxy configuration also rewrites the URL for a subdirectory, the test suite will fail because it relies on the absolute root path for HTTP requests. This is a known issue and a patch has been submitted by Jack Moffitt at https://issues.apache.org/jira/browse/COUCHDB-321.

Related Solutions

Nginx 502 bad gateway – fastcgi not listening? (Debian 5)

On my server I use nginx+fcgi as well.

My solution isn't foolproof but at least works. I have this script which uses spawn-fcgi and php5-cgi under /etc/init.d/

#!/bin/bash
PHP_SCRIPT='/usr/bin/spawn-fcgi -a 127.0.0.1 -p 9000 -u www-data -f /usr/bin/php5-cgi'
RETVAL=0
case "$1" in
    start)
      $PHP_SCRIPT
      RETVAL=$?
  ;;
    stop)
      killall -9 php5-cgi
      RETVAL=$?
  ;;
    restart)
      killall -9 php5-cgi
      $PHP_SCRIPT
      RETVAL=$?
  ;;
    *)
      echo "Usage: php-fastcgi {start|stop|restart}"
      exit 1
  ;;
esac
exit $RETVAL

and the related nginx conf is this:

server {
        location ~ .php$ {
                        fastcgi_pass 127.0.0.1:9000;
                        fastcgi_index index.php;
                        include /etc/nginx/fastcgi.conf;
                        fastcgi_param SCRIPT_FILENAME /var/www/hyperblasted/$fastcgi_script_name;
        }
        ...
}

and the fastcgi.conf contains the following

fastcgi_param GATEWAY_INTERFACE CGI/1.1;
fastcgi_param SERVER_SOFTWARE nginx;
fastcgi_param QUERY_STRING $query_string;
fastcgi_param REQUEST_METHOD $request_method;
fastcgi_param CONTENT_TYPE $content_type;
fastcgi_param CONTENT_LENGTH $content_length;
fastcgi_param REQUEST_URI $request_uri;
fastcgi_param DOCUMENT_URI $document_uri;
fastcgi_param DOCUMENT_ROOT $document_root;
fastcgi_param SERVER_PROTOCOL $server_protocol;
fastcgi_param REMOTE_ADDR $remote_addr;
fastcgi_param REMOTE_PORT $remote_port;
fastcgi_param SERVER_ADDR $server_addr;
fastcgi_param SERVER_PORT $server_port;
fastcgi_param SERVER_NAME $server_name;

Hope this helps :)

PS: With this setup I had an issue where the cgi daemon would die every now and then. I worked around this issue by executing this in a cronjob every 5 minutes:

if ps aux | grep 'php5-cgi' | grep -v grep  > /dev/null ; then
        echo "PHP-cgi is runnning !"    
else
        echo "PHP-cgi is down. Starting over..."
        /etc/init.d/php-fcgi start
fi

Nginx+ uwsgi gives 502 Bad Gateway

This error usually indicates that your Django application has crashed (raised an unhandled exception). You should be able to get more information from the uwsgi logs at /var/log/uwsgi.

Best Answer

Related Solutions

Nginx 502 bad gateway – fastcgi not listening? (Debian 5)

Nginx+ uwsgi gives 502 Bad Gateway

Related Topic