TLS V1.1 support deprecation

Modified on: Mon, 30 Mar, 2020 at 1:08 PM

We will be replacing the older version of Freshdesk with the new Mint experience on January 31, 2019. All your data and configurations will remain intact. Switching back to the old Freshdesk will not be possible. To read about this feature on Freshdesk Mint, refer to this article instead

This feature is currently not available on Freshdesk Mint.

This feature is not available on the old Freshdesk.

Applicable plans

SproutBlossomGardenEstateForest

From the 30th of April 2020 (PST), Freshdesk will be moving away from the TLS 1.1 version and will disable the encryption protocol across all its services. The deprecation will have effects on all Freshdesk customers currently using TLS 1.1, and it is advised that you check if you're going to be affected.

A quick guide to checking browser and mobile OS compatibility:

Desktop browser compatibility:Browsers released post August 2015 are TLS 1.2 compatible by default, and you need not worry about TLS 1.1 support deprecation.

In case your browsers are not installed or updated post August 2015, use the link - https://caniuse.com/#feat=tls1-2 to find out if this change will affect your business.

Set up an API client in a test environment. This could be any software that you are using to integrate with Freshdesk or any custom integration code that you have written.

In that test environment, change the API client's endpoint hostname from yourdomain.freshdesk.com to tlsv2test.freshdesk.com.

If you see a '401 Unauthorized' error, then this test passed. This response means that the underlying TLS connection was successful, despite the '401 Unauthorized' error.

If you instead see an error message that involves TLS or https, then the test has failed. Your API client will require adjustments or upgrades. Please check with your client's documentation on how to upgrade to TLS 1.2 support.

Example using cURL (the following test cases were run on cURL version 7.50.0):