Showing posts with label godaddy. Show all posts
Showing posts with label godaddy. Show all posts

Wednesday, October 28, 2026

Updating your godaddy certs during the G2 intermediate hierarchy to the TLS Root CA - R1 hierarchy

 

If you use GoDaddy TLS certificates you should be aware of some changes during the transition from the G2 Intermediate certificates to the new R1 Intermediate Certificates.

Browsers such as chrome are not taking the new R1 intermediate certificate and is labeling it as untrusted.  On IIS and Apache this is an easy fix by installing the R1 to G2 Cross Certificate into your intermediate certificate store.  However with apache tomcat it is not so simple a fix.

I have two servers that use apache tomcat and the configuration is a little bit different for each server and it is due to the software provider and how they configured it.  One is something called Horizon Web Services and the other is Papercut.

The following process using openssl worked for fixing horizon web services, however getting papercut was far more frustrating to fix.  You will need openssl installed I am using the version for windows, but this can also be done on Linux.  

First off when you download your certificates from GoDaddy, you will also need to go get the GoDaddy TLS Root CA - R1 to G2 Cross Certificate and the GoDaddy TLS Root CA - R1.  

The TLS R1 to G2 Cross Certificate will need to be installed in your intermediate certificate library on windows and the TLS Root CA - R1 will need to go in your trusted root certificate library.  On apache you will need to add the certs to your apache2 cert library typically located at /etc/ssl/certs/.  

For Apache tomcat, you will need to generate a new cert (I used a PFX PKCS#12 Generated certificate) including the GoDaddy TLS Room CA - R1 to G2 Cross Certificate as the certificate is just generated with the R1 intermediate certificate.  add the certs to your windows library as well if your hosting tomcat on windows otherwise you will need to add it to your certificate key.

PS C:\OpenSSL .\openssl pkcs12 -export -out tomcat.pfx -inkey "$PathToKey\$CertKey.key" -in "$Path2Cert\$CERT.crt" -certfile "$Path2Intermediate\$IntermediateCert.crt.pem" -keypbe AES-256-CBC -certpbe AES-256-CBC -macalg SHA256

Once that was created I copied the cert to the tomcat server; now replacing the certificate in the server config was not enough; I had to append the certificate to the pfx using keystore-explorer.  So I Opened the Root-R1-Cross-G2.crt and made 3 different certs to append to the pfx file r1crossg2_1.crt, r1crossg2_2.crt and r1crossg2_3.crt as shown below.


Once that is done you will need to restart the service or computer for the changes in the certificate to take affect.  Chrome may lag behind if you don't shut the browser down and relaunch it after you added the certificates to the server.


For papercut I could not use the same process for updating the certificate.  No matter how many different times or ways I used openssl to generate the certificate; I would get a certificate error on the server for papercut.

What I eventually ended up doing was taking my tomcat certificate library for Horizon Web Services and using Keystore Explorer convert from the pxf (Save as) it to a jks format and put that in place.

That got the certificate to finally be recognized in chrome without issue.



Updating your godaddy certs during the G2 intermediate hierarchy to the TLS Root CA - R1 hierarchy

  If you use GoDaddy TLS certificates you should be aware of some changes during the transition from the G2 Intermediate certificates to the...