Forums

For one of my domains the URL shows up like this: www.mydomainone.com/init/default/index

My other domain is ok, the URL is as it should be: www.myotherdomain.com

When I set up mydomainone.com on my pythonanywhere account I probable didn't do it the right way.

Please kindly advise.

Hi there, again, am not a web2py expert, so you may find the web2py mailing list is more helpful, but is this something to do with setting up your default application, or routes maybe?

Thanks for the reply, the issue is that I have 2 apps here and both are set up exactly the same, the default application is the same and the routes are the same. Yet, the URL is different. I can't figure out why.

BTW: when you say: " but is this something to do with setting up your default application" I am not sure I understand, one of my apps is the default app? Can you please explain what you mean by the default app? Thanks very much.

Does this help? http://www.ridgesolutions.ie/index.php/2013/02/20/web2py-make-your-app-the-default-web-application/

Thanks for the link. Ok, that helps. So, when I add several a domains to my pythonanywhere account I still only get one web2py framework for my account, regardless how many domains/apps I have? This means, I use one framework for all my apps where only one of my apps can be the default app and only that one can have the naked URL without the /init/default/index?

There are other issues, I started an other topic about this but I mention it here too as this is only happening to one of my apps not the other one so obviously something is wrong with the set up,

This is what the visitors to my site see right now instead of my website:

Your connection is not private

Attackers might be trying to steal your information from www.mydomain.com (for example, passwords, messages, or credit cards).

Again, this is only happening to one of my sites, not the other one.

ok i'll answer in the other tread.

As I mentioned on the other thread, the request.requires_https() was uncommented in the db.py in web2py for some reason for this site so now I commented it and the https connection is not forced so I don't get the warning and it also fixed the www.mydomainone.com/init/default/index problem. Now it's:http:// www.mydomainone.com instead of https:// www.mydomainone.com/init/default/index

Looks like everything is fixed by commenting the request.requires_https()