hendy wrote: > no - that's what i was trying to express: https://lalala/ does _not_ work. > but: http://lalala:443/ _works_ (somehow, i don't know why - do you?) I suspect you have a rather confused httpd.conf. Especially since you are attempting NBVH with SSL (which is not possible). Try working through your VHs and explicitly adding the port numbers so you can see exactly what is what. E.g. NameVirtualHost 192.168.1.1:80 Listen 80 <VirtualHost 192.168.1.1:80> ServerName <plain http site 1 name> DocumentRoot <plain http site 1 content> ..... </VirtualHost> <VirtualHost 192.168.1.1:80> ServerName <plain http site 2 name> DocumentRoot <plain http site 2 content> ..... </VirtualHost> Listen 443 <VirtualHost 192.168.1.1:443> ServerName <SSL site name> DocumentRoot <SSL site content> SSLEngine on SSLCertificateFile etc. ..... </VirtualHost> If you do this, you will quickly see if you have a plain http virtualhost on port 443 (which is what I suspect). > > Are you *sure* they're on different IPs? > > i am 100% sure, yes. Let me rephrase the question: Does your computer think they are on different ports? Please do: # nslookup www.nouse.net # nslookup books.6340.org and see what it says. > > > [05/Jul/2001 20:58:48 23793] [warn] Init: You should not use name-based > > > virtual hosts in conjunction with SSL!! >i have the same certificate for > books.lala and lala (as said above..) Aha! That is why NBVH seems to work. Rgds, Owen Boyle. ______________________________________________________________________ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
