openvqn不会设置，求大佬帮忙

guo***

Thu Feb 25 21:28:46 2021 Openvirtual** 2.4.7 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Feb 21 2019
Thu Feb 25 21:28:46 2021 Windows version 6.2 (Windows 8 or greater) 64bit
Thu Feb 25 21:28:46 2021 library versions: OpenSSL 1.1.0j  20 Nov 2018, LZO 2.10
Thu Feb 25 21:28:46 2021 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
Thu Feb 25 21:28:46 2021 Need hold release from management interface, waiting...
Thu Feb 25 21:28:46 2021 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
Thu Feb 25 21:28:46 2021 MANAGEMENT: CMD 'state on'
Thu Feb 25 21:28:46 2021 MANAGEMENT: CMD 'log all on'
Thu Feb 25 21:28:46 2021 MANAGEMENT: CMD 'echo all on'
Thu Feb 25 21:28:46 2021 MANAGEMENT: CMD 'bytecount 5'
Thu Feb 25 21:28:46 2021 MANAGEMENT: CMD 'hold off'
Thu Feb 25 21:28:46 2021 MANAGEMENT: CMD 'hold release'
Thu Feb 25 21:28:49 2021 MANAGEMENT: CMD 'username "Auth" "pjUTo5d32AA8FumFJCiSrBaK"'
Thu Feb 25 21:28:49 2021 MANAGEMENT: CMD 'password [...]'
Thu Feb 25 21:28:49 2021 WARNING: --ping should normally be used with --ping-restart or --ping-exit
Thu Feb 25 21:28:49 2021 NOTE: --fast-io is disabled since we are running on Windows
Thu Feb 25 21:28:49 2021 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Thu Feb 25 21:28:49 2021 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Thu Feb 25 21:28:49 2021 TCP/UDP: Preserving recently used remote address: [AF_INET]184.170.244.219:1194
Thu Feb 25 21:28:49 2021 Socket Buffers: R=[65536->65536] S=[65536->65536]
Thu Feb 25 21:28:49 2021 UDP link local: (not bound)
Thu Feb 25 21:28:49 2021 UDP link remote: [AF_INET]184.170.244.219:1194
Thu Feb 25 21:28:49 2021 MANAGEMENT: >STATE:1614259729,WAIT,,,,,,
Thu Feb 25 21:29:49 2021 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Thu Feb 25 21:29:49 2021 TLS Error: TLS handshake failed
Thu Feb 25 21:29:49 2021 SIGUSR1[soft,tls-error] received, process restarting
Thu Feb 25 21:29:49 2021 MANAGEMENT: >STATE:1614259789,RECONNECTING,tls-error,,,,,
Thu Feb 25 21:29:49 2021 Restart pause, 5 second(s)

guo***

求大佬解答一下

nets***

搬运：

Troubleshooting
If the ping failed or the Open××× client initialization failed to complete, here is a checklist of common symptoms and their solutions:

    You get the error message: . This error indicates that the client was unable to establish a network connection with the server.
     
    Solutions:
        Make sure the client is using the correct hostname/IP address and port number which will allow it to reach the Open××× server.
        If the Open××× server machine is a single-NIC box inside a protected LAN, make sure you are using a correct port forward rule on the server's gateway firewall. For example, suppose your Open××× box is at 192.168.4.4 inside the firewall, listening for client connections on UDP port 1194. The NAT gateway servicing the 192.168.4.x subnet should have a port forward rule that says forward UDP port 1194 from my public IP address to 192.168.4.4.
        Open up the server's firewall to allow incoming connections to UDP port 1194 (or whatever TCP/UDP port you have configured in the server config file).
    You get the error message: Initialization Sequence Completed with errors -- This error can occur on Windows if (a) You don't have the DHCP client service running, or (b) You are using certain third-party personal firewalls on XP SP2.
     
    Solution: Start the DHCP client server and make sure that you are using a personal firewall which is known to work correctly on XP SP2.
    You get the Initialization Sequence Completed message but the ping test fails -- This usually indicates that a firewall on either server or client is blocking ××× network traffic by filtering on the TUN/TAP interface.
     
    Solution: Disable the client firewall (if one exists) from filtering the TUN/TAP interface on the client. For example on Windows XP SP2, you can do this by going to Windows Security Center -> Windows Firewall -> Advanced and unchecking the box which corresponds to the TAP-Win32 adapter (disabling the client firewall from filtering the TUN/TAP adapter is generally reasonable from a security perspective, as you are essentially telling the firewall not to block authenticated ××× traffic). Also make sure that the TUN/TAP interface on the server is not being filtered by a firewall (having said that, note that selective firewalling of the TUN/TAP interface on the server side can confer certain security benefits. See the access policies section below).
    The connection stalls on startup when using a proto udp configuration, the server log file shows this line:
     

        TLS: Initial packet from x.x.x.x:x, sid=xxxxxxxx xxxxxxxx

    however the client log does not show an equivalent line.
    Solution: You have a one-way connection from client to server. The server to client direction is blocked by a firewall, usually on the client side. The firewall can either be (a) a personal software firewall running on the client, or (b) the NAT router gateway for the client. Modify the firewall to allow returning UDP packets from the server to reach the client.

See the FAQ for additional troubleshooting information.

Ke***

楼主你解决问题了吗
我也是同样报错日志
我感觉这条才是主因，IP地址ping不通
WARNING: --ping should normally be used with --ping-restart or --ping-exit
我试了防火墙白名单openvirtual**.exe，也试了打开端口都没用
然后我借了个其他供应商的IP，试了试可以成功PING通
就感觉是自己用的服务器，被自己的网络运营商给封锁了，所有节点的IP都ping不通