GaborO
GoTo Contributor
Joined 4 years ago
User Profile
User Widgets
Contributions
Re: Cached Credentials no longer work?
Hi RobertHabib, We've upgraded to OpenSSL 3.0.x in the new version. The old key, which was generated by an older OpenSSL version, might not be accepted by the 3.0.x version. Especially if the error message is "RSA_check_key returned with invalid RSA key: error:0200007B:lib(4)::reason(123)"46Views1like0CommentsRe: Can not connect with client app
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" -createsc1.8KViews2likes1CommentRe: Can not connect with client app
Hi Jahmil! Welcome to the GoTo Community. It seems that the new version of LogMeIn service cannot load its old certificate. To fix it no need to reinstall LogMeIn. Run this command in an administrator command prompt on the computer you want to access, to regenerate the service's certificate: "C:\Program Files (x86)\LogMeIn\x64\LogMeIn.exe" cert -createca -createsc Please note that auto-login from the client will fail for the first time. Then it should be working.1.8KViews0likes6CommentsRe: Login without having to type a password no longer works on mobile
Hi Sensible_Ray! Your problem might be that the service's cannot load its certificate and it has to be regenerated. Try this command on: 64 bit Windows: "C:\Program Files (x86)\LogMeIn\x64\LogMeIn.exe" cert -createca -createsc 32 bit Windows: "C:\Program Files\LogMeIn\x86\LogMeIn.exe" cert -createca -createsc Then restart the LogMeIn service.1.1KViews1like0CommentsRe: No Connection
Hi Azores44! According to the screenshot, the Hamachi client on your workplace computer is not online or is not online in the same network. So, please, check if: - the Hamachi Tunneling Engine (or Hamachi2Svc) is running, - the client is online, connected to the server (the client/computer name is displayed in the second row, below the IP adresses), and - the client is online in the same network (a green dot is displayed in front of the name, written in bold black).2.2KViews2likes1CommentRe: Hamachi Network in Gateway Mode is Giving Gateway an APIPA Address
Hi LuisGTO, In Windows domain environment workstation computers are not allowed to function as a gateway client. This is kind of a "security" related restriction. You need to try on a workstation which is not in domain or on a server computer.2.7KViews1like0Comments