Thanks Anthony, that's the problem - I hadn't opened port 443 in my
iptables. I knew it would be something silly. It works now.
I also had to change a couple of other things to make it work. Would either
of the below compromise the security of my setup?
1. I removed the "-u www-data" option in the line of the script that sets
the admin password, because I don't have a user called www-data. So, my
script says something like:
sudo python -c "from gluon.main import save_password;
save_password(raw_input('admin password: '),443)"
Should I create a user called www-data, and if so what privileges should I
give them? Sorry if this is a naive question.
2. I had to add sudo for the following commands in the script, otherwise
they wouldn't run
sudo start uwsgi-emperor
sudo /etc/init.d/nginx restart
I'm guessing that once again this is because I don't have a user called
www-data, and I haven't updated the uid and gid lines of the uwsgi config
file to reflect the user that I'm running as.
Tobias
P.S. For completeness, here's the whole script I'm using to launch the
server now:
# Set the password for the administrative interface
cd /home/www-data/web2py
sudo python -c "from gluon.main import save_password;
save_password(raw_input('admin password: '),443)"
# Stop server if it was already running
sudo stop uwsgi-emperor
sudo /etc/init.d/nginx stop
# Start the server
sudo start uwsgi-emperor
sudo /etc/init.d/nginx restart
On 17 February 2014 20:09, Anthony <[email protected]> wrote:
> Why are you port forwarding? Is SSL still on port 443?
>
> Anthony
>
>
--
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
