Chris F. 

Normally it's better to click on that small disk symbol to get the full error stack and not just the headlines.  You can add the file you save when you do that to your post using Insert -> Code and paste the code into the Code box, or just attach the xml file you get and this will be automatically added to a code box.

However, the part you shared that refers to the secure channel failure probably tells us all we need to know.  Please review this notice from DeepL:

https://developers.deepl.com/docs/resources/breaking-changes-change-notices/july-2024-deprecation-of-insecure-cipher-suites

The new deadline for them making their changes expired a couple of days ago so we do expect to see some users having problems.  The full stack would have told us what version of Windows you are running so I cannot be 100% sure about this... so please verify if the Windows version you are using supports TLS 1.2 and TLS 1.3.  Older versions of Windows (like Windows 7) may not have full support for these protocols without manual configuration or updates.

In a nutshell this is something you need to address... we cannot help with this.

Chris F. 

I would also add that if you use the add-on for DeepL through the Studio Cloud Capabilities instead of the plugin then I don't think you'll have the same problem because that will be using our servers instead of your computer, and we are definitely compliant.