Okay, here we go again.
I can now generate certificates, and keystores are created properly, to
the best of my knowledge. I'm setting the CN to the FQDN I'm using to
test, and secure-site.xml is a copy of the default web site, except with a
keystore specified and, of course, secure="true", and the port is changed
to "443" instead of "80".
When I start Orion, it spends a minute or two seeding the key, which was
expected.
However, when I try to pull up the https://my.site.name/, I get a site not
available immediately. (IE says "Cannot find server or DNS error," despite
being able to pull up "http://my.site.name/" with no issues.)
What am I missing here? I was originally setting the certificate's CN to
something irrelevant (my name, actually, as keytool implied); that's been
changed to match a hostname I can pull up via my browser. I'm still
lost. :(
-----------------------------------------------------------
Joseph B. Ottinger [EMAIL PROTECTED]
http://cupid.suninternet.com/~joeo HOMES.COM Developer
