Find the problem. :-)
The chained certificates has been loaded as a non-chained certificate, only the first certificate in the file has been loaded, so it will not be trusted by browsers.
With the updated RC3 release, chained certificates should have the same effect as server certificate + CA certificate.
I hope it is the cause of the connection problem as well. :-)