You probably had erase you parameters.py file when you install the new version... Did you made a backup?
If so, just copy/paste the 443 parameters py files from the archive into the web2py folder of the new 2.0.8 installation. If you didn't make a backup, what you can do is in order to create a new parameters.py file is to boot with the built-in server define the password you want to use when prompting for a password... Then get the parameters.py file that the start of web2py will have generated, copy/paste it into your prod server the one with the new 2.0.8 web2py, rename it parameters_443.py. Make sure your web2py in the prod server is down before copying the parameter.py file. If you use linux box with apache to make sure web2py is down, you only have to shutdown apache like this : sudo /etc/init.d/apache2 stop The parameter.py is only a file containing en encrypted or hash (don't remember) of the password you setup when installing web2py. Hope it helps Richard On Mon, Sep 17, 2012 at 3:15 PM, David Phillips < [email protected]> wrote: > I had a web2py 1.99.7 app running on Elastic Beanstalk. I was able to use > the admin interface over https. I then upgraded web2py to 2.0.8 and > uploaded it to EB. Now I am getting this message when I try to access the > admin interface over HTTPS: > > ATTENTION: Login requires a secure (HTTPS) connection or running on > localhost. > > Another change I notice is that request.is_https no longer seems to be > true. > > I see that the format of the parameters_*.py file has changed. Is there > any reason why I can no longer use the admin interface? > > Thanks. > > -- > > > > --
