The script you mentioned is based on upstart but on the raspberry-pi the init script are handled by sysvinit. So that, I'd say that uwsgi is not running? Try to run it manually:
sudo uwsgi --master --die-on-term --emperor /etc/uwsgi --logto /var/log/ uwsgi/uwsgi.log Paolo On Sunday, August 24, 2014 11:00:49 AM UTC+2, Encompass solutions wrote: > > Hi, > Currently I am getting a 502 Bad Gateway Error when trying to access my > web2py server running on Raspberry Pi. > I first tried the setup with the script setup-web2py-nginx-ubuntu.sh as > it's nearly identical to the instructoins found here. > http://web2py.com/books/default/chapter/29/13#Nginx > After doing the script I got the 502 Bad Gateway error. > I know I am on the right server as I can see the request in the logs. > I then went through the tutorial on the website I previously mentioned and > still got the error. > There were a few differences in the script. For example web2py.ini verses > web2py.xml (which is informationally the same.) > > Any ideas on how to diagnose this and find the correct solution? > > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- 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/d/optout.
