The issue is characterised by a sudden inability for all users to register, sync or send error logs. It affects Create v8.6 and v10.0 – 10.4.
The problem occurs when a customer IT team blocks communications from their computers that use an older internet protocol called TLS. TLS version 1.2 is the standard now but the default for applications built on .NET Framework 4.6 (e.g. Create 10.0 – 10.4) is V1.1. There are three solutions:
- Revert the change that blocks TLS 1.1 (This would be the least secure option)
- Change a registry setting described in this article: https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls#systemdefaulttlsversions
- Upgrade to Create v10.5, which is built on .NET Framework 4.7.2.
Create is built on .NET Framework 4.6.1 which does support TLS 1.2 but uses TLS 1.1 as the default. If you wanted to reinstate that change in the future, there is a registry setting that forces .NET to use the TLS version dictated by the operating system rather than the Framework version. Here’s an article covering this:
https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls#systemdefaulttlsversions
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article