OpenVPN W10 socket protect error

[Jippy]

Hi everyone

I have a strange one where I can't get one computer out of 6 or 7 machines so far to connect to my VPN hosted through my Synology NAS. All the machines run Windows 10 Home and are either a desktop machine I custom assembled, or a variant of a Lenovo Yoga or Thinkpad laptop. I was also able to connect my Android phone without issue, there is just this one machine (one of the Lenovo's) that just won't connect.

I have tried allowing an exception to the firewall, disabling the firewall altogether, disabling the anti-virus, checking all the settings against the other machines, flushing the DNS, disabling IPv6 and short of throwing the computer in the bin and buying a new one, tried just about all else.

The log is showing a "socket_protect error (UDP)" and it just attempts to reconnect, brings this error, disconnects, attempts again, rinse and repeat. It has declining so quickly that it feels like it is a firewall issue, however as I mentioned, I disabled that and it did not change anything. The log on the server end is not even showing an attempt by this username to log in which helps cement the suspiction it is being blocked at the local machine end.

It is frustrating that it is just this one machine so far in isolation doing this.

Does anyone have any ideas as to what is causing this?

My configuration (although I doubt this is the issue as it is working on all the other machines):

View OriginalVPN Config

1

2

3

dev tun

4

5

tls-client

6

7

8

9

Remote was here and removed

10

11

12

13

# The "float" tells OpenVPN to accept authenticated packets from any address,

14

15

# not only the address which was specified in the --remote option.

16

17

# This is useful when you are connecting to a peer which holds a dynamic address

18

19

# such as a dial-in user or DHCP client.

20

21

# (Please refer to the manual of OpenVPN for more information.)

22

23

24

25

#float

26

27

28

29

# If redirect-gateway is enabled, the client will redirect it's

30

31

# default network gateway through the VPN.

32

33

# It means the VPN connection will firstly connect to the VPN Server

34

35

# and then to the internet.

36

37

# (Please refer to the manual of OpenVPN for more information.)

38

39

40

41

#redirect-gateway def1

42

43

44

45

# dhcp-option DNS: To set primary domain name server address.

46

47

# Repeat this option to set secondary DNS server addresses.

48

49

50

51

#dhcp-option DNS DNS_IP_ADDRESS

52

53

54

55

pull

56

57

58

59

# If you want to connect by Server's IPv6 address, you should use

60

61

# "proto udp6" in UDP mode or "proto tcp6-client" in TCP mode

62

63

proto udp

64

65

66

67

script-security 2

68

69

70

71

72

73

comp-lzo

74

75

76

77

reneg-sec 0

78

79

80

81

cipher AES-256-CBC

82

83

84

85

auth SHA512

86

87

88

89

auth-user-pass

90

91

<ca>

92

--STRIPPED INLINE CA CERT--

93

</ca>

94

1

dev tun

2

tls-client

3

Remote was here and removed

4

pull

5

proto udp

6

script-security 2

7

comp-lzo

8

reneg-sec 0

9

cipher AES-256-CBC

10

auth SHA512

11

auth-user-pass

12

<ca>

13

--STRIPPED INLINE CA CERT--

14

</ca>

[oconf=][/oconf]

[makiavelli]

Hello,

I have exactly the same issue on my home network as well. I have OpenVPN server configured on EC2 instance, and only 1 out of 3 machines can't connect to it. All 3 machines are running macOS Catalina 10.15.3 OS and all 3 machines are using native OpenVPN Connect client software

Here is the log from the client side software:
Transport error: socket_protect error

There are no logs falling on server side

[Jippy]

I have sorted my machine out, I don't know what went wrong. I just uninstalled and reinstalled OpenVPN, nothing different about how it installed, used the same certificate and config file, it connected. Very strange! Have you tried that makiavella? It seems very basic "turn it off and on again" type stuff but surprisingly, it actually worked this time!!!

[cika8]

Hi there.
I had the same problem. It's OpenVPN on Synology server, and we have 10 clients on it. We configured VPN on all 10 clients, and everything was perfect, no drops, disconnects, etc...
After few days I wanted to connect to VPN - it stucks (trying to connect)... Checked everything, Firewall, router, asked IT on workplace, asked ISP, even tried to make hotspot from another ISP, installed ProtonVPN to give me another IP and the result is that I couldn't connect to VPN with 4 different IPs (even I tried with another OpenVPN account).
After that I installed OpenVPN on Android and successfully connects from Mobile? With same ISP, same IP which PC uses (I mean dynamic IP, not private) and same config file, same account.
When I went to log it says: "Transport Error: socket_protect error (UDP)" and spent 2h on Google what is that and how to solve.
Finally, I uninstalled OpenVPN and installed again, loaded config file and everything is working now... How?
After me, 2 clients experienced the same problem, but they could connect via hotspot or another ISP.
Can someone check is there any problem with UDP protocol or driver or VPN or something else?

View OriginalClient config

1

2

3

dev tun

4

5

tls-client

6

7

8

9

remote X.X.X.X 1194

10

11

12

13

pull

14

15

16

17

proto udp

18

19

20

21

script-security 2

22

23

24

25

comp-lzo

26

27

28

29

reneg-sec 0

30

31

32

33

cipher AES-256-CBC

34

35

36

37

auth SHA512

38

39

40

41

auth-user-pass

42

43

44

45

client-cert-not-required

46

47

48

49

<ca>

50

--STRIPPED INLINE CA CERT--

51

</ca>

52

1

dev tun

2

tls-client

3

remote X.X.X.X 1194

4

pull

5

proto udp

6

script-security 2

7

comp-lzo

8

reneg-sec 0

9

cipher AES-256-CBC

10

auth SHA512

11

auth-user-pass

12

client-cert-not-required

13

<ca>

14

--STRIPPED INLINE CA CERT--

15

</ca>

Thanks & Regrads.

Edit: The last version of OpenVPN connect is used, 3.2.2 (1455)
OS is Windows 10 (20H2), with latest updates.

[stipa]

It seems that product in question is OpenVPN Connect, which is a proprietary product by OpenVPN Inc and not a community project. Please contact OpenVPN Connect support.

[cika8]

Thanks!
It seems that problem is fixed by switching to fiber optic cable (instead of previous satellite, same ISP) in workplace. Everything is now working good (on every client).
I know that this is not related to topic, but maybe it will be useful for someone.

Wish you happy New year!

[Titiviking]

Check if the service is disabled or not.
Newer installations of the OpenVPN client rely on an agent installed as a service.
By default it is set to Automatic. However when putting it to manual and rebooting, I faced the same errors.

Reinstall would remove the service and reinstall it with automatic startup. That is why reboot seems to 'fix' it.

Service:

Code: Select all

OpenVPN Agent agent_ovpnconnect                          Running             Automatic           Local System
OpenVPN Connect Helper Service                                               Manual              Local System

[axsdenied]

Good tip on checking the service, that worked for me. That said, the service was already set to automatic so why wasn't it running? Did the service crash?

[DesertShadow]

I get the socket protect error AND the service is running... Any other ideas?

[wesowens13]

I had the same problem on my MacOS with the M1 running Ventura.
It ended up being that a service was set to run at startup by OpenVPN Connect that was required in order to connect. I normally disable startup services by default on my MAC, and this was causing the issue.
Fix:
1. Go to "Login Items" in the Settings for the Mac.
2. Enable the OpenVPN Client Option in the Menu.
3. Restart

I now can run OpenVPN without errors and I've tested it over multiple restarts. Much better than uninstalling and reinstalling the App everytime.

I tried starting the service manually and running the program, but I have not found a manual way to fix the issue. I'm sure there is a way to start the service through a terminal and then set it up as a script. I was able to get it to work if I don't use OpenVPN Connect and instead run the openvpn command installed through homebrew, which is easier than writing a new script to start the service.

[jordan.stevens]

Thank you! Life Saver!

[jery]

same error socket protecion 30