Maybe the self signed certificate has an unacceptable length?

The following two posts might help to get an understanding of what needs to be done.

http://www.assono.de/blog/d6plinks/Creating-Self-Certified-SSL-Certificates-Valid-Longer-Than-One-Year
https://plus.google.com/104457100541403655061/posts/eZ8gqmDVcG9

Essentially you'll need to patch the Server Certificate Administration template to increase the default key length

Hello,

I've installed a new Traveler 9 server in an existing Domino domain (with 8.5.3 servers), domain where a Traveler 8.5.3 already exists.
So there are purposely two Traveler servers, not clustered. (It's for testing V9 before move some users to it).
The names.nsf Template is in v9 only on the Traveler V9 server, the administration server has in names.nsf still in 8.5.3 (design replication is unchecked).

I've just created a self-signed certificate on the Traveler V9 for testing SSL access, but when testing to connect with external ip address to it, we are redirected on the 1rst Traveler server. (which have another IP address).
The rules seems to have been correctly set on the firewall for the two separated servers, but we are always redirected on the 1rst one, with a certificate error.

I don't find what's the problem.