On Thu, Jan 04, 2001 at 07:52:01AM -0800, David Rees wrote:
> On Thu, Jan 04, 2001 at 04:16:33PM +0100, Owen Boyle wrote:
> > > > What I'm going to do is to start documenting which browsers work and which
> > > > browsers don't work with various settings.
> > > >
> > > > If everyone could go and hit http://spoke.nols.com:8080/ and then
> > > > https://spoke.nols.com:8443/ and then report their success/failure.
> >
> > This is a laudable aim but I suspect many users will be like me - unable
> > to connect to your sites because they use non-standard port numbers
> > which our corporate firewalls block. Would it be possible to set up the
> > sites on 80 and 443?
>
> Moving the server to port 443 is on my list of things to do. :-) Need to
> get some free time, maybe tonight.
I've moved the server to port 443 so now you should be using
https://spoke.nols.com/ to reach the server.
I was going to create a new certificate with the proper server-name
(self-signed), but I keep on getting this error and Netscape cannot
connect to the server complaining that the certificate wasn't properly
signed:
CA verifying: server.crt <-> CA cert
server.crt: /C=US/ST=California/L=San Diego/O=David
[EMAIL PROTECTED]
error 18 at 0 depth lookup:self signed certificate
/C=US/ST=California/L=San Diego/O=David
[EMAIL PROTECTED]
error 7 at 0 depth lookup:certificate signature failure
This happens when signing the certificate. Anyone have any ideas? I've
done this before without any problems, and I'm following the directions on
the FAQ to the letter...
Thanks,
Dave
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
