Re: [web2py] Re: Hosting question

2019-08-02 Thread Jose C
Glad to have helped. Cheers, On Friday, 2 August 2019 09:40:05 UTC+1, Rahul wrote: > > Hi Jose, > Thank you !! That worked ... the point #4 resolved that issue. So > now no need to work with Apache and all is working well. Thanks a million!! > artpic.in and targetsoft.co.in work fine

Re: [web2py] Re: Hosting question

2019-08-02 Thread Rahul Dhakate
Hi Jose, Thank you !! That worked ... the point #4 resolved that issue. So now no need to work with Apache and all is working well. Thanks a million!! artpic.in and targetsoft.co.in work fine now. Regards, Rahul On Fri, Aug 2, 2019 at 1:53 PM Jose C wrote: > Hi Rahul, > > ok,.. > 1)

Re: [web2py] Re: Hosting question

2019-08-02 Thread Jose C
Hi Rahul, ok,.. 1) no the routes.examples.py files don't cause any problems. 4) Can you make sure that both *'www.domain.in': 'app1'* as well as *'domain.in': 'app1'* are specified in the domains key of the BASE dict? I would hope this finally resolves your issue. I don't have any experience

Re: [web2py] Re: Hosting question

2019-08-02 Thread Rahul Dhakate
Hi Jose, Thanks for getting back - I am using nano for editing routes.py in the live server, it isn't so friendly but gets the job done. Might be one of the reasons for my typo - Here are the answers to rest of the questions - 1) First of all, can you confirm this is a routes.py file in

Re: [web2py] Re: Hosting question

2019-08-01 Thread Jose C
Strange... 1) First of all, can you confirm this is a routes.py file in the web2py root directory and that there are not any routes.py (app-specific routers) files present in the app directories as well (that could be overriding the main routes.py)? 2) The config I posted is my live config

[web2py] Re: Hosting question

2019-08-01 Thread Paco Bernal
Thank you, Now it's working as spected. appconfig.ini [host] > names = subdomain:* > I removed the virtualhost regarding the dedicated ips and set DocumentRoot in port 80 for my subdomain to /dev/null Not sure if it's the right way but it's working now without expliciting having a

[web2py] Re: Hosting question

2019-08-01 Thread Dave S
On Thursday, August 1, 2019 at 1:37:37 AM UTC-7, Jose C wrote: > > I use Lets encrypt certificates and redirecting from 80 to 443, and I >> don't touch virtualhost file in port 80 so for sure, i'm doing something >> wrong with apache3 and for sure with host names in appconfig.ini >> >> [host]

Re: [web2py] Re: Hosting question

2019-08-01 Thread Rahul Dhakate
Hi Jose, I did the changes as per your suggestion. Now when I specify a default application it takes me to the same application when I access any domain. Secondly - If I specify my domain name without a www. prefix (example: artpic.in) I am navigated to welcome however the app is not show

[web2py] Re: Hosting question

2019-08-01 Thread Jose C
> > I use Lets encrypt certificates and redirecting from 80 to 443, and I > don't touch virtualhost file in port 80 so for sure, i'm doing something > wrong with apache3 and for sure with host names in appconfig.ini > > [host] >> names = localhost:*, 127.0.0.1:*, *:*, * >> >> That is worrying.

Re: [web2py] Re: Hosting question

2019-08-01 Thread Jose C
> > > Have you removed welcome application from web2py applications folder > or it still resides there but when accessed gives 404? I am using python > 2.7.13 . I will try your settings for routes and get back to you. > Normally I always delete the app, but for testing this issue I left

[web2py] Re: Hosting question

2019-08-01 Thread Paco Bernal
Yes, I discovered a few days ago that private folder can be accessed using the vps ip, so I have been playing with host names in appconfig.ini and with apache2 configuration and the only way to stop accessing private folder was adding a new virtualhost in apache for each vps ip with this: >

Re: [web2py] Re: Hosting question

2019-08-01 Thread Rahul Dhakate
Hi Jose, Have you removed welcome application from web2py applications folder or it still resides there but when accessed gives 404? I am using python 2.7.13 . I will try your settings for routes and get back to you. In the meantime you may access the sites here that I referred to - 1.

[web2py] Re: Hosting question

2019-08-01 Thread Jose C
> > > I added the line in routes.py - While it restricts allowing > access to other applications like welcome it does not restrict > redirection - so in my case it still redirected to welcome application > mentioning something is wrong message. > > Odd. I have a similar setup to you

[web2py] Re: Hosting question

2019-08-01 Thread Rahul
Hi Jose, I added the line in routes.py - While it restricts allowing access to other applications like welcome it does not restrict redirection - so in my case it still redirected to welcome application mentioning something is wrong message. *Paco,* I checked for this

[web2py] Re: Hosting question

2019-07-31 Thread Jose C
> I want to avoid this and the users must only get redirected to the two sites that are hosted. What should I do ? Two options. 1) remove the default welcome app from your live server (simply delete the directory). 2) Add this key to your BASE dict (which basically tells web2py which apps