The GoTo Community is currently experiencing some technical issues affecting new posts and comments. We are actively working with our service provider and apologize for the frustration.

Forum Discussion

Danny6's avatar
Danny6
New Contributor
2 years ago
Solved

Error when connecting. (Error occurred error: 14094410:lib(20):func(148):reason(1040))

Getting this error when connecting to a client. So far only one member of my team can connect to this client but everyone else gets this error.
  • GlennD's avatar
    GlennD
    2 years ago

    Here is the solution for computers showing this error due to an expired certificate:

    As admin, open the command prompt of my computer in LogMeIn Client
    1. cd "C:\Program Files (x86)\LogMeIn\x64"
    2. cmd
    3. logmein.exe cert -createca "LogMeIn CA on %COMPUTERNAME%" -createsc "%COMPUTERNAME%"
    4. net stop LogMeIn && net start LogMeIn

    (Thank you Michal_orc )

     

    Depending on where the computer is located, you may run into an error "Country too long". 

     

    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 

    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

     

    On Mac the certificates are stored in files:

    - /Library/Application Support/LogMeIn/CA.pem

    - /Library/Application Support/LogMeIn/server_ex.pem

     

    First these files have to be deleted: 

    - sudo rm /Library/Application Support/LogMeIn/CA.pem

    - sudo rm /Library/Application Support/LogMeIn/server_ex.pem

     

    Then restart the daemon: 

    - sudo launchctl stop com.logmein.logmeinserver 

     

Dazzman's avatar
Dazzman
Active Contributor
2 years ago

I have tried the fix it and it worked on a system when I was logged in as a full admin user, trying to do it as a normal system user generated an error when the command script ran as that account did not have enough system access rights for it to process correctly.

GlennD's avatar
GlennD
GoTo Manager
2 years ago

Here is the solution for computers showing this error due to an expired certificate:

As admin, open the command prompt of my computer in LogMeIn Client
1. cd "C:\Program Files (x86)\LogMeIn\x64"
2. cmd
3. logmein.exe cert -createca "LogMeIn CA on %COMPUTERNAME%" -createsc "%COMPUTERNAME%"
4. net stop LogMeIn && net start LogMeIn

(Thank you Michal_orc )

 

Depending on where the computer is located, you may run into an error "Country too long". 

 

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 

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

 

On Mac the certificates are stored in files:

- /Library/Application Support/LogMeIn/CA.pem

- /Library/Application Support/LogMeIn/server_ex.pem

 

First these files have to be deleted: 

- sudo rm /Library/Application Support/LogMeIn/CA.pem

- sudo rm /Library/Application Support/LogMeIn/server_ex.pem

 

Then restart the daemon: 

- sudo launchctl stop com.logmein.logmeinserver 

 

  • stefannyTique's avatar
    stefannyTique
    New Member
    2 years ago

    Buen dia,

     

    Me soluciona el error, pero la momento de apagar el equipo y encenderlo al otro dia debo generar nuevamente le comendo por cmd para que me genere la conexion y no pueod generar esto todo el tiempo

  • JP93's avatar
    JP93
    Visitor
    2 years ago

    Hi GlennD ,

                                We have a user in our environment experiencing this issue, however she has a Macbook. Can you list the steps on how updating the SSL can be done on a Mac?

     

    Thanks 

    • GlennD's avatar
      GlennD
      GoTo Manager
      2 years ago

      Hi JP93, welcome to the community.

       

      Great question, I will add this to the Solution post.

       

      On Mac the certificates are stored in files:

      - /Library/Application Support/LogMeIn/CA.pem

      - /Library/Application Support/LogMeIn/server_ex.pem

       

      First these files have to be deleted: 

      - sudo rm /Library/Application Support/LogMeIn/CA.pem

      - sudo rm /Library/Application Support/LogMeIn/server_ex.pem

       

      Then restart the daemon: 

      - sudo launchctl stop com.logmein.logmeinserver 

       

      • Sergio_Boening's avatar
        Sergio_Boening
        Visitor
        2 years ago

        What about windows users? where can I find those folders?