Guest User!

You are not Sophos Staff.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Connect Client 2.2.90.1104 SSL VPN error: 0x20000000 / 0x0000274D

Had a few Win10 clients recently that received that error when they tried to establish the SSL VPN connection.

The issue could be resolved by a client restart.

As I've never seen that error, can you please describe what it means? The log looks like there is some issue with the openvpn service but it was running. If it was'nt the error would have been different.

scgui
2023-04-06 09:11:10AM [10856] inf Sophos-Connect-Version: 2.2.90.1104
2023-04-06 09:11:10AM [10856] inf strongSwan-Version: 5.9.5
2023-04-06 09:11:10AM [10856] inf OpenVPN-Version: 2.5.6.0
2023-04-06 09:11:16AM [10856] dbg Geben Sie die Benutzer-Anmeldeinformationen ein
2023-04-06 09:11:29AM [10856] inf Verbindung xxxxx.xxxxxxxxxx.xx wird hergestellt
2023-04-06 09:11:43AM [10856] dbg SSL-VPN-Fehler: 0x20000000


scvpn
2023-04-06 09:11:02AM [2468] inf Starting Sophos Sophos Connect version 2.2.90.1104
2023-04-06 09:11:02AM [2468] dbg Initializing protected storage
2023-04-06 09:11:02AM [2468] inf Logged on user is xxxxxxxxx\xxxxxxxxxxxx
2023-04-06 09:11:02AM [2468] dbg Starting the auto-importer
2023-04-06 09:11:02AM [2468] inf Initializing strongSwan
2023-04-06 09:11:04AM [2468] dbg strongSwan version 5.9.5 has been started
2023-04-06 09:11:05AM [2468] inf Initializing open vpn service
2023-04-06 09:11:05AM [2468] dbg Starting the communications module
2023-04-06 09:11:05AM [2468] dbg Starting HTTP server on 127.0.0.1:60110
2023-04-06 09:11:05AM [2468] inf Sophos Connect started
2023-04-06 09:11:10AM [2076] dbg Sending telemetry data to sftelemetry.sophos.com:443
2023-04-06 09:11:29AM [2608] dbg xxxxx.xxxxxxxxxx.xx VPN state changed to connecting
2023-04-06 09:11:29AM [2608] dbg Starting tunnel (connecting)
2023-04-06 09:11:29AM [2608] inf Remote added to list: xxxxx.xxxxxxxxxx.xx 443
2023-04-06 09:11:31AM [2608] dbg xxxxx.xxxxxxxxxx.xx VPN state changed to disconnecting
2023-04-06 09:11:42AM [2608] err OpenVpnMgmt::open_management_socket socket connect failed:0x0000274D
2023-04-06 09:11:42AM [2608] dbg Can't create tunnel - failed to start ovpn
2023-04-06 09:11:42AM [4404] dbg xxxxx.xxxxxxxxxx.xx VPN state changed to disconnected
2023-04-06 09:11:42AM [4404] dbg Sending notification: SSL VPN error: 0x20000000


openvpn
2023-04-06 09:11:31 OpenVPN 2.5.6 Windows-MSVC [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Apr 22 2022
2023-04-06 09:11:31 Windows version 10.0 (Windows 10 or greater) 64bit
2023-04-06 09:11:31 library versions: OpenSSL 1.1.1n  15 Mar 2022, LZO 2.10
2023-04-06 09:11:31 MANAGEMENT: Socket bind failed on local address [AF_INET]127.0.0.1:25340
2023-04-06 09:11:31 Exiting due to fatal error



This thread was automatically locked due to age.
Parents
  • Hi LHerzog,

    Thank you for reaching out to Sophos Community.

    I've found a similar case where user experiences an SSL VPN error: 0x20000000

    • The main ISP was down, and the other alternate ISP was in the backup. Updated the alternate ISP from backup to Active, Connected successfully.
    • Gateway IP Address wasn’t added in the configuration. Re-input and re-download the config file tried to ping and got the replies successfully.

    Kindly check if this is applicable to your case and if the gateway IP Address configuration is still the same when the issue re-occurs.

    Erick Jan
    Community Support Engineer | Sophos Technical Support
    Sophos Support Videos Product Documentation  |  @SophosSupport  | Sign up for SMS Alerts
    If a post solves your question use the 'Verify Answer' link.

Reply
  • Hi LHerzog,

    Thank you for reaching out to Sophos Community.

    I've found a similar case where user experiences an SSL VPN error: 0x20000000

    • The main ISP was down, and the other alternate ISP was in the backup. Updated the alternate ISP from backup to Active, Connected successfully.
    • Gateway IP Address wasn’t added in the configuration. Re-input and re-download the config file tried to ping and got the replies successfully.

    Kindly check if this is applicable to your case and if the gateway IP Address configuration is still the same when the issue re-occurs.

    Erick Jan
    Community Support Engineer | Sophos Technical Support
    Sophos Support Videos Product Documentation  |  @SophosSupport  | Sign up for SMS Alerts
    If a post solves your question use the 'Verify Answer' link.

Children
No Data