Try removing the backslashs

On Sun, Sep 9, 2012 at 8:55 PM, Martin Weissenboeck <[email protected]>wrote:

> Dear all,
> I have tried to use web2py together with Apache. The book says how to
> write the configuration file:
>
> <VirtualHost *:80>
>   ServerName web2py.example.com
>   *WSGIDaemonProcess web2py user=www-data group=www-data \
>                            display-name=%{GROUP}*
>   WSGIProcessGroup web2py
>   WSGIScriptAlias / /users/www-data/web2py/wsgihandler.py
> ...
> </VirtualHost>
>
>
> <VirtualHost *:443>
>   ServerName web2py.example.com
>   SSLEngine on
>   SSLCertificateFile /etc/apache2/ssl/server.crt
>   SSLCertificateKeyFile /etc/apache2/ssl/server.key ...
> </VirtualHost>
>
>
> But I got the following message:
>
>
> Daemon process called 'web2py' cannot be accessed by this WSGI application: 
> /users/www-data/web2py/wsgihandler.py
>
>
>
> On 
> http://modwsgi.readthedocs.org/en/latest/configuration-directives/WSGIDaemonProcess.html
>  I found:
>
>
> *If the WSGIDaemonProcess directive is specified outside of all virtual
> host containers, any WSGI application can be delegated to be run within
> that daemon process group. If the WSGIDaemonProcess directive is specified
> within a virtual host container, only WSGI applications associated with
> virtual hosts with the same server name as that virtual host can be
> delegated to that set of daemon processes.*
>
> Therefore I changed the configuration and I had success.
>
>
> *WSGIDaemonProcess web2py user=www-data group=www-data \
>                            display-name=%{GROUP}*
> <VirtualHost *:80>
>   ServerName web2py.example.com
>
>   WSGIProcessGroup web2py
>   WSGIScriptAlias / /users/www-data/web2py/wsgihandler.py
> ...
> </VirtualHost>
> <VirtualHost *:443>
>   ServerName web2py.example.com
>   SSLEngine on
>   SSLCertificateFile /etc/apache2/ssl/server.crt
>   SSLCertificateKeyFile /etc/apache2/ssl/server.key
> ...
> </VirtualHost>
>
>
> Maybe this should be changed in the book?
>
>
> Regards, Martin
>
>  --
>
>
>
>

-- 



Reply via email to