Skip to main content
We’ve updated our Terms of Service. A new AI Addendum clarifies how Stack Overflow utilizes AI interactions.
added 71 characters in body
Source Link
Orca
  • 1
  • 1

I faced same issue "TLS handled error" and solved by changing UDP to TCP(Both server and client config: proto tcp ).

If you already checked Official FQA.(e.g.: firewall-cmd, iptables, cloud platform ingress rule) Then make sure the UDP packets arrived at OpenVPN server side. Use

tcpdump -i <inf> udp port 1194 # inf is network interface name. use ifconfig to get 

If network connectivity is ok, then you can see something like:

tcpdump content

This indicates OpenVPN server do send result to your OpenVPN client via UDP port 1194. But OpenVPN client not receive the result packets.

Many reasons leads to this result, your ISP block UDP, or company block UDP. So change to TCP and try.

Updating

The client cannot receive any packets 8 minutes after successfully connected to server using TCP proto.

Finnally I figured out that China GFW can detecte OpenVPN protocal and block it.

If you from China mainland, just change another VPN plan.Ya~~~(中国的小伙伴,放弃使用OpenVPN吧)

I faced same issue "TLS handled error" and solved by changing UDP to TCP(Both server and client config: proto tcp ).

If you already checked Official FQA. Then make sure the UDP packets arrived at OpenVPN server side. Use

tcpdump -i <inf> udp port 1194 # inf is network interface name. use ifconfig to get 

If network connectivity is ok, then you can see something like:

tcpdump content

This indicates OpenVPN server do send result to your OpenVPN client via UDP port 1194. But OpenVPN client not receive the result packets.

Many reasons leads to this result, your ISP block UDP, or company block UDP. So change to TCP and try.

Updating

The client cannot receive any packets 8 minutes after successfully connected to server using TCP proto.

Finnally I figured out that China GFW can detecte OpenVPN protocal and block it.

If you from China mainland, just change another VPN plan.Ya~~~(中国的小伙伴,放弃使用OpenVPN吧)

I faced same issue "TLS handled error" and solved by changing UDP to TCP(Both server and client config: proto tcp ).

If you already checked Official FQA.(e.g.: firewall-cmd, iptables, cloud platform ingress rule) Then make sure the UDP packets arrived at OpenVPN server side. Use

tcpdump -i <inf> udp port 1194 # inf is network interface name. use ifconfig to get 

If network connectivity is ok, then you can see something like:

tcpdump content

This indicates OpenVPN server do send result to your OpenVPN client via UDP port 1194. But OpenVPN client not receive the result packets.

Many reasons leads to this result, your ISP block UDP, or company block UDP. So change to TCP and try.

Updating

The client cannot receive any packets 8 minutes after successfully connected to server using TCP proto.

Finnally I figured out that China GFW can detecte OpenVPN protocal and block it.

If you from China mainland, just change another VPN plan.Ya~~~(中国的小伙伴,放弃使用OpenVPN吧)

added 298 characters in body
Source Link
Orca
  • 1
  • 1

I faced same issue "TLS handled error" and solved by changing UDP to TCP(Both server and client config: proto tcp ).

If you already checked Official FQA. Then make sure the UDP packets arrived at OpenVPN server side. Use

tcpdump -i <inf> udp port 1194 # inf is network interface name. use ifconfig to get 

If network connectivity is ok, then you can see something like:

tcpdump content

This indicates OpenVPN server do send result to your OpenVPN client via UDP port 1194. But OpenVPN client not receive the result packets.

Many reasons leads to this result, your ISP block UDP, or company block UDP. So change to TCP and try.

Updating

The client cannot receive any packets 8 minutes after successfully connected to server using TCP proto.

Finnally I figured out that China GFW can detecte OpenVPN protocal and block it.

If you from China mainland, just change another VPN plan.Ya~~~(中国的小伙伴,放弃使用OpenVPN吧)

I faced same issue "TLS handled error" and solved by changing UDP to TCP(Both server and client config: proto tcp ).

If you already checked Official FQA. Then make sure the UDP packets arrived at OpenVPN server side. Use

tcpdump -i <inf> udp port 1194 # inf is network interface name. use ifconfig to get 

If network connectivity is ok, then you can see something like:

tcpdump content

This indicates OpenVPN server do send result to your OpenVPN client via UDP port 1194. But OpenVPN client not receive the result packets.

Many reasons leads to this result, your ISP block UDP, or company block UDP. So change to TCP and try.

I faced same issue "TLS handled error" and solved by changing UDP to TCP(Both server and client config: proto tcp ).

If you already checked Official FQA. Then make sure the UDP packets arrived at OpenVPN server side. Use

tcpdump -i <inf> udp port 1194 # inf is network interface name. use ifconfig to get 

If network connectivity is ok, then you can see something like:

tcpdump content

This indicates OpenVPN server do send result to your OpenVPN client via UDP port 1194. But OpenVPN client not receive the result packets.

Many reasons leads to this result, your ISP block UDP, or company block UDP. So change to TCP and try.

Updating

The client cannot receive any packets 8 minutes after successfully connected to server using TCP proto.

Finnally I figured out that China GFW can detecte OpenVPN protocal and block it.

If you from China mainland, just change another VPN plan.Ya~~~(中国的小伙伴,放弃使用OpenVPN吧)

added 5 characters in body
Source Link
Orca
  • 1
  • 1

I faced same issue "hanled"TLS handled error" and solved by changing UDP to TCP(Both server and client config: proto tcp ).

If you already checked Official FQA. Then make sure the UDP packets arrived at OpenVPN server side. Use

tcpdump -i <inf> udp port 1194 # inf is network interface name. use ifconfig to get 

If network connectivity is ok, then you can see something like:

tcpdump content

This indicates OpenVPN server do send result to your OpenVPN client via UDP port 1194. But OpenVPN client not receive the result packets.

Many reasons leads to this result, your ISP block UDP, or company block UDP. So change to TCP and try.

I faced same issue "hanled error" and solved by changing UDP to TCP(Both server and client config: proto tcp ).

If you already checked Official FQA. Then make sure the UDP packets arrived at OpenVPN server side. Use

tcpdump -i <inf> udp port 1194 # inf is network interface name. use ifconfig to get 

If network connectivity is ok, then you can see something like:

tcpdump content

This indicates OpenVPN server do send result to your OpenVPN client via UDP port 1194. But OpenVPN client not receive the result packets.

Many reasons leads to this result, your ISP block UDP, or company block UDP. So change to TCP and try.

I faced same issue "TLS handled error" and solved by changing UDP to TCP(Both server and client config: proto tcp ).

If you already checked Official FQA. Then make sure the UDP packets arrived at OpenVPN server side. Use

tcpdump -i <inf> udp port 1194 # inf is network interface name. use ifconfig to get 

If network connectivity is ok, then you can see something like:

tcpdump content

This indicates OpenVPN server do send result to your OpenVPN client via UDP port 1194. But OpenVPN client not receive the result packets.

Many reasons leads to this result, your ISP block UDP, or company block UDP. So change to TCP and try.

Source Link
Orca
  • 1
  • 1
Loading