I keep getting 502 Bad Gateway, and I'm not sure why. I followed the Nginx
deployment recipe on the website, with the following changes:
/etc/uwsgi/web2py.xml: Used /var/www-data/web2py/ instead of
/home/www-data/web2py/
nginx conf: server_name is my server ip (I don't have a domain name)
instead of $hostname. I also changed the location to /web2py instead of
root.
Here is my nginx conf:
server {
listen 443 default_server ssl;
server_name xxx.xxx.xxx.xxx;
ssl_certificate /etc/nginx/ssl/server.crt;
ssl_certificate_key /etc/nginx/ssl/server.key;
ssl_prefer_server_ciphers on;
ssl_session_cache shared:SSL:10m;
ssl_session_timeout 10m;
ssl_ciphers ECDHE-RSA-AES256-SHA:DHE-RSA-AES256-SHA:DHE-DSS-AES256-
SHA:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA;
ssl_protocols SSLv3 TLSv1;
keepalive_timeout 70;
location /web2py {
#uwsgi_pass 127.0.0.1:9001;
uwsgi_pass unix:///tmp/web2py.socket;
include uwsgi_params;
uwsgi_param UWSGI_SCHEME $scheme;
uwsgi_param SERVER_SOFTWARE nginx/$nginx_version;
}
}
I omitted http since I only want to test over https for now.
Restarted both uwsgi and nginx in that order. uwsgi seems to find web2py
okay in their logs:
announcing my loyalty to the Emperor...
*** vassal web2py.xml is now loyal ***
When I access "https://<server ip>/web2py", I get the 502 error.
Nginx error.log says:
2013/08/29 18:10:08 [error] 9793#0: *4 upstream prematurely closed
connection while reading response header from upstream, client:
xxx.xxx.xxx.xxx, server: xxx.xxx.xxx.xxx, request: "GET /web2py HTTP/1.1",
upstream: "uwsgi://unix:///tmp/web2py.socket:", host: "xxx.xxx.xxx.xxx.
I'm running ubuntu 13.04 server, if that's any use.
--
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
