I've definitely got parameters_443.py and parameters_8000.py in the /var/web2py directory. No parameters_80.py file to note though. I tried the https login in a guessing game to succeed. I'm at a stalemate. I'm a chemist not a programmer per se. The web2py issued ticket was copy/pasted from the browser after plugging in the raw ISP IP. http://75.87.135.60 ------ which returns with:
http://75.87.135.60/welcome/default/index and the aforementioned ticket. The cherokee-admin -b based startup has been employed for a few days now. I discovered it from http://blog.e-shell.org/279 though it's described in theCherokee with FastGGIsection of The Official web2py Book. Dale On Sun, Mar 27, 2011 at 12:10 PM, pbreit <[email protected]> wrote: > Hmmm...I don't use Cherokee anymore but will try to have a look. Is that a > Web2py-issued ticket? Setting up SSL on Cherokee took me a few tries. > > Also, do you see "parameters_443.py" in your web2py directory? If you > see "parameters_80.py" you can duplicate it and rename it. "443" is the SSL > port which is required for admin when you're not on localhost. > > Another trick on Cherokee is to run admin like this: > > $ cherokee-admin -b > > This avoids needing to set up the SSH tunnel so you can more easily access > your Cherokee admin. The "-b" means you are binding to all ports. It's > discouraged because it's a *very* small security risk for the shot period of > time that admin is active. >
