Thank you Mario. I had the password file for the secure port but inside no 
password. I copied the password from my development machine and it worked. 
Don't understand it but your post gave me a clue where to look. Thanks!

On Sunday, February 12, 2012 6:11:12 AM UTC-6, Mariano Reingart wrote:
>
> The admin is not mandatory, you can upload your chages via FTP.
>
> Also, you can create a password file (parameters_xxxx.py, replace xxx
> with the port number) just running web2py in your local machine, and
> then upload it too your server (copy it to the folder where web2py.py
> resides).
>
> Best regards,
>
> Mariano Reingart
> http://www.sistemasagiles.com.ar
> http://reingart.blogspot.com
>
> On Sun, Feb 12, 2012 at 7:57 AM, Edward Shave
>  wrote:
> > Hi, despite being a total novice with little or no experience beyond 
> windows
> > I have managed to install web2py on a webfaction shared server. By
> > substituting my webfaction application listening port into the 
>  instructions
> > I found here...
> > 
> http://docs.webfaction.com/user-guide/databases.html#starting-an-ssh-tunnel-with-putty
>    I
> > can connect to my web2py application over SSH. Problem is when I try to
> > access admin I get.... " admin disabled because unable to access password
> > file".
> >
> > I found a lot of references to this error when searching the group but no
> > real answer. There was some talk of admin using port 80 maybe when 
> looking
> > for the password? Another suggestion was that I should have two 
> instances of
> > web2py running on the server but I think that's only necessary if admin 
> has
> > been disabled, which in my case I don't think it has. Either way I don't
> > know how to go about fixing it.
> >
> > Here you can find the web2py install script I used...
> >  
> http://community.webfaction.com/questions/7193/install-web2py-with-nginx-and-uwsgi
> >
> > One last question... Is there any need to access admin on the server? I'm
> > wondering if I can just make changes localy then upload the changes via 
> ftp?
>
>

Reply via email to