Hi Joseph,
do you have a central truststore configured for your IS, that goes on top of the cacerts file from the JVM?
Looks like the GoDaddy Root certificate is part of the cacerts file from the JVM.
In this case add the GoDaddy Secure certificate to this truststore in IS and restart the IS.
I would avoid changing the cacerts file of the JVM as this can be overwritten when the JVM gets updated.
Place your private key and the corresponding certificate (signed by GoDaddy Secure?) in a PKCS#12 file and configure this as a Keystore in IS.
Can you share your Keystore, Certificates and Port Configuration pages for further analysis, please?
Can you check the certificate chain when connecting via browser to your Server via https?
Regards,
Holger
#Integration-Server-and-ESB#webMethods#Enterprise-Gateway