After I have installed my new Verisign Global ID server certificate, the browsers complain that they cannot verify the server certificate?
That is because Verisign uses an intermediate CA certificate between the root CA certificate (which is installed in the browsers) and the server certificate (which you installed in the server). You should have received this additional CA certificate from Verisign. If not, complain to them. Then configure this certificate with the SSLCertificateChainFile directive in the server. This makes sure the intermediate CA certificate is send to the browser and this way fills the gap in the certificate chain.
Related Questions
- After I have installed my new Verisign Global ID server certificate, the browsers complain that they cannot verify the server certificate?
- What is the difference between a VeriSign 40-bit SSL Certificate and a 128-bit Global Server ID?
- Why do browsers complain that they cannot verify my Verisign Global ID server certificate?