So you managed to survive a whole year after getting your certificate, congratz, and now you need to replace it with a new one because the old one is about to expire. Here are the simple steps to do that:
- Go to Godaddy and ask them to issue the new certificate. You can use the CSR file you used last time you asked for a certificate.
- Download the certificate files, you’ll get two files with a CRT extension: your site’s certificate, and go daddy’s CA certificate
- Append your site’s certificate to go daddy’s. On unix, this would be cat your.crt godaddy.crt > finalcert.crt
- Validate that the certificate you created works for your deployment:
bees app:cert:validate -a yourcloudbeesaccount -cert ./finalcert.crt -pk ./thekeyfileyougotwhenyoucreatedthecsrfile.key
- Update your deployment with the new certificate (you need to know the name of the ssl service you created on cloudbees, check your production app on cloudbees for this setting):
bees app:router:update yoursslservicename-ssl -cert ./finalcert.crt -pk ./thekeyfileyougotwhenyoucreatedthecsrfile.key
That’s it, you should now have a valid new certificate live.