On Wednesday, September 1, 2010, nitin chandra <[email protected]> wrote:
> In httpd.conf I have commented the line which activates "httpd-ssl.conf"
> following is my http-vhost.conf file.
> ******************************
> NameVirtualHost *:80
>
> <VirtualHost *:80>
> ServerAdmin [email protected]
> DocumentRoot "/opt/apache2215/docs/dummy-host.example.com"
> ServerName dummy-host.example.com
> ServerAlias www.dummy-host.example.com
> ErrorLog "logs/dummy-host.example.com-error_log"
> CustomLog "logs/dummy-host.example.com-access_log" common
> </VirtualHost>
>
> <VirtualHost *:80>
> ServerAdmin [email protected]
> DocumentRoot "/opt/apache2215/docs/dummy-host2.example.com"
> ServerName dummy-host2.example.com
> ErrorLog "logs/dummy-host2.example.com-error_log"
> CustomLog "logs/dummy-host2.example.com-access_log" common
> </VirtualHost>
>
> <VirtualHost *:80>
> ServerName www.healthcare.in
> ServerAlias healthcare.in
>
> Alias /wsgi-scripts/ /wsgi-scripts/
Get rid of the above Alias directive, it is not needed.
> WSGIDaemonProcess healthcare.in processes=6 threads=15
> display-name=%{GROUP}
> WSGIProcessGroup healthcare.in
>
> WSGIScriptAlias / /wsgi-scripts/myapp.wsgi
What do you get for running:
ls -las /wsgi-scripts
>
> <Directory /wsgi-scripts>
> Order allow,deny
> Allow from all
> </Directory>
> </VirtualHost>
> *******************************************
>
>>
>> Can we go backwards. What URL are you using. If using above URL that
>> is the issue. You have:
>>
>> WSGIScriptAlias /wsgi-scripts /home/dev/wsgi-scripts/myapp.wsgi
>>
>> so should be:
>>
>> http://192.168.1.6/wsgi-scripts
>>
For the way you have the configuration at the moment, should be just:
http://www.healthcare.in/
You can't use IP address.
What do get for:
grep healthcare /etc/hosts
Ie., does that address even resolve to your own system?
If that FQDN does actually resolve to your Apache and you use that
URL, should be fine so long as that VirtualHost is actually being
picked up.
Graham
> did not work.
>
>> and possibly even:
>>
>> http://www.healthcare.com/wsgi-scripts
>>
> changed from .com to .in still the same ...
>
>> because if you have multiple virtual hosts, the IP would not
>> necessarily map to the virtual host you just set up.
>>
>> As I asked before, can you reconfirm the configuration you are using
>> for HTTP host, plus also state what URL you are using.
>
> in main httpd.conf
>
> Listen
>
>
>>
>> Also indicate whether www.healthcare.com is even resolvable and
>> contactable as that machine. Ie.,
>>
>> ping www.healthcare.com
>>
>> Does that work and is the target actually your machine?
>>
>> Graham
>>
>> Graham
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "modwsgi" group.
>> To post to this group, send email to [email protected].
>> To unsubscribe from this group, send email to
>> [email protected].
>> For more options, visit this group at
>> http://groups.google.com/group/modwsgi?hl=en.
>>
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "modwsgi" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/modwsgi?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"modwsgi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/modwsgi?hl=en.
