Hi Jerzy Czopik ,

I just tried to connect right now, and the login worked on my side:

If you are still experiencing the same issue, please try to login to the Trados Team account via web browser. If it wrks from the web browser then try to reset the local Trados Team connection (Language Cloud connection):

https://gateway.sdl.com/apex/communityknowledge?articleName=000015275

I hope this helps.

Alex J.

Alex Jude 

Thank you. Unfortunately this does not work either, there is no such LC file in the said folder. Must be something different. I can live with it for the moment, as I need to deliver a job fast, so I will deal with the problem later.

Jerzy Czopik  if the web browser access doesn't work either, it is probably related to the firewall or the antivirus. One of these 2 is blocking the connection to Trados Team.

In this case you can try adding the following web addresses to the Firewall/Antivirus exception list:

• lc-api.sdl.com
• languagecloud.sdl.com
• cxc-languagecloud.sdl.com
• sdl-prod.eu.auth0.com
• www.sdl.com
• sdl.com
• oos.sdl.com
• dc.services.visualstudio.com (optional)
• 1.1.1.1  - Starting with Trados Studio 2021 SR1 CU4
• cdn.auth0.com
• www.rws.com
• es-languagecloud.sdl.com
• esr-languagecloud.sdl.com
• io-languagecloud.sdl.com
• logi-languagecloud.sdl.com
• tm-maintenance-languagecloud.sdl.com
• google-translate.sdl.com
• languagecloud.sdl.com/cp/login

I hope this helps.

Alex J.

Alex Jude 

Many thanks for your efforts.

I should have mentioned, that I am testing a beta and this is the only version of Studio, where the LC access does not work. It does not affect the production version, so my question here was a dumb one, sorry. Please simply disregard, the LC login works as expected when using a proper version.

Jerzy Czopik , can you specify which Beta version? I checked with the latest beta build: 17.0.3.11695, and it worked as expected.

It is newer, not yet official. I've got some special task.

Alex Jude said:

Jerzy Czopik  if the web browser access doesn't work either, it is probably related to the firewall or the antivirus. One of these 2 is blocking the connection to Trados Team.

In this case you can try adding the following web addresses to the Firewall/Antivirus exception list:

• lc-api.sdl.com
• languagecloud.sdl.com
• cxc-languagecloud.sdl.com
• sdl-prod.eu.auth0.com
• www.sdl.com
• sdl.com
• oos.sdl.com
• dc.services.visualstudio.com (optional)
• 1.1.1.1  - Starting with Trados Studio 2021 SR1 CU4
• cdn.auth0.com
• www.rws.com
• es-languagecloud.sdl.com
• esr-languagecloud.sdl.com
• io-languagecloud.sdl.com
• logi-languagecloud.sdl.com
• tm-maintenance-languagecloud.sdl.com
• google-translate.sdl.com
• languagecloud.sdl.com/cp/login

I hope this helps.

Alex J.

it's work for me. Thk Alex 

pou

Jerzy Czopik  Recently I have been investigating similar issue and the root cause was the TLS 1.3 security protocol enabled on the affected computer. At the moment this is not compatible with Trados Studio and Trados Team connection. Here are the steps for your to check on your side:

1. Open the Registry Editor of your computer (administrator rights may be required)
2. Go to Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols from Registry editor
3. Find "TLS 1.3" and delete it
4. Open Trados Studio, and try connecting to the server/cloud again

I hope this helps you solve the issue on your end.

Alex J.

Jerzy Czopik  Recently I have been investigating similar issue and the root cause was the TLS 1.3 security protocol enabled on the affected computer. At the moment this is not compatible with Trados Studio and Trados Team connection. Here are the steps for your to check on your side:

1. Open the Registry Editor of your computer (administrator rights may be required)
2. Go to Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols from Registry editor
3. Find "TLS 1.3" and delete it
4. Open Trados Studio, and try connecting to the server/cloud again

I hope this helps you solve the issue on your end.

Alex J.

Alex Jude 

Thanks.
However, it looks like the problem was only connected to the beta I was testing. With the production version everything works as expected.