Hello all,
i'm new to the list and apache-ssl in general, so go easy :-)
I'm working on setting up a secure web server for a company which
doesn't yet have a domain name registered, however it has been requested
that i configure a test server for people to view, and so that the site
can be up and running as quickly as the domain name can be had. I have
had few problems compiling and installing SSLeay, and Apache-SSL
(against 1.3.0), but am having a few configuration troubles.
at this site, there is a main host (not ssl), and a virtual host on port
443 (ssl-enabled). when i sit down at the machine and type
http://localhost/, everything works smoothly. when i type
https://localhost:443/, i am whisked away to the secure virtual host.
the problem is when i am not at the machine locally, or type in the
server's ip address. the main site works, but the secure site does not
(a la: https://209.96.3.21:443/). netscape eventually times out, citing
"unable to connect to server (TCP Error: No route to host)"
My simple guesses as to the cause of this problem come from remedial
logical deduction only, not technical expertise. as i do not have a
domain name to work with, i certainly have not been able to purchase a
digital certificate, so i have simply generated one with make
certificate. also, since i don't have a domain name, i have inserted
localhost for the servername, as requested in make certificate, (i
haven't had much luck with ip addresses) - perhaps this would explain
the discrepancy between a request for a secure server name and an ip
address? if perhaps this sound plausible, is there a way around it? or
if not, does anyone have any other ideas? i would be more than happy to
post pieces of the server configuration file, but thought that would be
poor etiquette.
obviously, any help anyone could give would be very much appreciated,
and thank you in advance!
ian wehrman
ian@wehrman.com