Workarounds for the 2018 TLS 1.2 Compatibility Issue

Owned by Samuel Valdez (Unlicensed)
Last updated: Sept 25, 2019 by Dan King (Unlicensed)Version comment
1 min read

On December 01, 2018, the EAS source code version control provider, Bitbucket, disabled support of TLSv1 and TLSv1.1 and began requiring secure connections through TLS 1.2.

The EAS stack does not currently support TLS 1.2 (as of January 2019). Until this issue is resolved, there are workarounds for deploying EAS source code to the respective servers.

See the following pages for the workaround for each environment:

Also see the following BitBucket issues for more detailed information:


There is no workaround required for the * * DB server because that deployment does not rely on resources stored in BitBucket.


Filter by label

There are no items with the selected labels at this time.