Please help, my production server is down because of this mess!!!!

I've been successfully using various version of Tomcat for serveral years
with the same certificate... all worked well.

The last server I was using was 5.0.28... which kept crashing every day!
Looking at the log files did not give any hint as to what was making it
crash.  Actually it didn't even seem to log anything out of the ordinary.

I wanted to test the stability of Tomcat 5.5.17, so I installed in on the
same server but renamed all the 8XXX ports to 9XXX so that it could be run
in parallel to the 5.0.28 server.  When I started the 5.5.17 server, I
noticed that I could not get the HTTPS (SSL) pages working correctly.  The
normal HTTP pages were working correctly though.

Then the real trouble started!!  I could not load any HTTPS pages from any
server thereafter...

The SSL pages DID work on the 5.0.28 prior to testing the 5.5.17, but now
HTTPS no longer works at all.  When trying to load the ssl pages from the
browser it says nothing... just a timeout occures.

The logs don't show a single trace that something (a page) was not properly
sent.

Using 'netstat -ln' shows that the ports are successfully bound.

The only message I'm capable of getting is with lynx:

bash>   lynx https://localhost:8443

Will display the following line:

 SSL error:Can't find common name in certificate-Continue? (y)

Appart from installing and running server 5.5.17, nothing has changed on my
server, so its weird that my production 5.0.28 should stop working because
of this test???

If you have questions, please ask...

Thanks in advance,

Jeach!

Reply via email to