> There nothing wrong in principle with your configuration and we know > of users who use it in a similar configurations.
Thank you for the quick reply. It is good to know that this *can* work. I saw one post elsewhere where someone said web2py *can't* be used in a subdirectory with mod_wsgi due to some issue with WSGI compliance. It was hard to believe. > When you say it does not work, what do you see? What kind of problems > do you experience? When I visit http://example.com/web2py-apps/ I get response 503 in the browser and the error_log says "(13)Permission denied: mod_wsgi (pid=10472): Unable to connect to WSGI daemon process 'web2py' on '/ etc/httpd/logs/wsgi.7370.102.1.sock' after multiple attempts." When I visit http://example.com/web2py-apps/welcome/default/index/ I get response 403 in the browser and the error_log says "client denied by server configuration: /home/siteadmin/web2py/wsgihandler.pywelcome" Web2py works if I use Python's built-in WSGI server, running as the same user that apache normally runs as. Mod_wsgi works normally if I use a different script, other than web2py. The only problem is getting them to work together. Alex
