Exciting changes are coming as we upgrade our community website. You may notice a fresh new look and some differences in how things work. We will post more details soon and canโ€™t wait to welcome you to our improved space!

Forum Discussion

Arai's avatar
Arai
Active Contributor
4 years ago
Solved

Can not connect with client app

I can not been able to connect from the client application since about October 2021. Show detail Negotiating SSL... SSL connected and negotiated the following cipher: Key exchange: TLS_AES_25...
GaborO's avatar
GaborO
GoTo Contributor
2 years ago

Hi Jahmil!

The problem is that Windows returns a 3-digit "sub-region-code" instead of the 2-character "alpha-2" country code. Check for example: https://github.com/lukes/ISO-3166-Countries-with-Regional-Codes/blob/master/all/all.csv 
Based on the 419 value, you might be in the Latin America and the Caribbean region.

I've seen this problem in Mexico.

To overcome on this problem you have to explicitly specify the 2-digit code of your country. So find the "alpha-2" code of your country in the table above and issue the following command in an administrator command prompt:

"C:\Program Files (x86)\LogMeIn\x64\LogMeIn.exe" cert -createca "Default CA" "<alpha-2 code of your coutry>" -createsc

For example if you are in Mexico, then issue the following command:

"C:\Program Files (x86)\LogMeIn\x64\LogMeIn.exe" cert -createca "Default CA" "MX" -createsc

Jahmil's avatar
Jahmil
Active Contributor
2 years ago

Thanks a lot GaborO

 

i follow your instructions, close & start LogMeIn and now works

 

i repeat thanks a lot