Thanks for the suggestion, but refreshing the page doesn't make a difference. I've tried setting up the ssh tunnel with different ports, etc., but I can't get editing to work. Seems as though it could be a permissions problem, but I can't see why there is a problem. It's also possible that it is some issue with the way I have nginx or uwsgi configured, but I'm stumped on that, too.
On Friday, June 21, 2013 1:03:59 PM UTC-4, Niphlod wrote: > > from web2py's standpoint (the web one) it only matters where requests are > from, not the user who's doing those. > If you have a working admin on the local LAN and you can access but not > edit from outside your LAN, than you're doing the ssh tunnel wrong. > > PS: did you just tried to do a ctrl+R to refresh all static assets while > on tunnel ? Problems can happen if you load an admin app in your local > computer using 127.0.0.1:8000 and then a remote (ssh tunneled) admin on > 127.0.0.1:8000 too. > If web2py's versions are different, your browser can't tell the difference > between one or another admin app, so it may retain in cache the "other" > version of admin's static files. > > On Friday, June 21, 2013 6:27:46 PM UTC+2, Woody wrote: >> >> I am using web2py admin served by nginx and uwsgi. When I access the >> server from the same LAN, I can edit files with no problem. When I use an >> ssh tunnel to proxy into my LAN from a remote location, I can login to the >> admin app and I can view files, but when I try to edit them, I get nothing >> in the edit window. I get no errors, just a blank edit window. >> >> The permissions used by the nginx, and uwsgi match the file ownership. >> If I change the ownership to 777, I still have the problem. Anybody have >> an idea what's causing this? >> > -- --- 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.
