Important Maintenance Notice: SSL Certificate Changes
Scheduled Maintenance Report for Chargebee
Postmortem

We have updated the SSL Certificate for *.chargebee.com.

If you are getting SSL handshake exception or unable to connect with Chargebee using our API, make sure you have our Root Certificate (DigiCert Global Root CA) in your certificate store.

You can also see the list of ciphers supported by Chargebee at https://www.ssllabs.com/ssltest/analyze.html?d=app.chargebee.com&hideResults=on

Posted almost 3 years ago. Dec 16, 2015 - 11:57 UTC

Completed
The scheduled maintenance has been completed.
Posted almost 3 years ago. Dec 16, 2015 - 11:31 UTC
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted almost 3 years ago. Dec 16, 2015 - 11:27 UTC
Scheduled
We will be updating our SSL Certificates from SHA1 to SHA256. There will not be any downtime for this change.

We have tested our API client libraries (PHP, Python & Ruby), where the certificate chain is bundled along with the client library. For other languages, you need to do an API call (say list subscription) to sha256.chargebee.com to confirm whether the API works.

If you get a 401 status with "Invalid API Key", there is no further action required and you're good to go. But if you encounter an SSL handshake exception, you need to import the latest CA (Certificate authority) to your certificate bundle.

If you need further assistance, email us at support@chargebee.com, and we'll gladly help you out!
Posted about 3 years ago. Dec 01, 2015 - 07:19 UTC