Hello,
wireguard connection, if condition > 1 peer
makes a connection attempt for each peer - 4 times,
those. if 4 peers - 16 connections,
on the 5th cycle, goes into Disabled status
If the number of peers = 1, - makes connection attempts > 20 times
Options do not help: Use randomly, Set the maximum number of handshake attempts before connecting
VpnClientPro 1.01.48
wireguard connection, if condition > 1 peer - desable after 4th cycle
Re: wireguard connection, if condition > 1 peer - desable after 4th cycle
Hello,
I'm sorry but this request is for a very specific configuration and therefore I don't think it's possible to add this option.
However the "Set the maximum number of handshake attempts before disconnecting" option may be useful and there are no reports that it works randomly.
The counter is reset every time a handshake is completed successfully.
I'm sorry but this request is for a very specific configuration and therefore I don't think it's possible to add this option.
However the "Set the maximum number of handshake attempts before disconnecting" option may be useful and there are no reports that it works randomly.
The counter is reset every time a handshake is completed successfully.
Re: wireguard connection, if condition > 1 peer - desable after 4th cycle
Can you check from your end?
On a 4-peer configuration.
With and without the "Set the maximum number of handshake attempts before disconnecting" option.
It is enough to register arbitrary peers (IP) so that they are not available via UDP (,
and you will see that after 4 cycles of checking, the connection itself goes into the Disable status,
It is normal that the number of peers > 1, and VPN Client Pro tries to connect one by one (I have 4 entry points, some of them may be unavailable at certain times)
But when all 4 points are not available, VPN Client Pro performs 4 check cycles and goes into Disable status - opening the way for traffic without VPN
Please Help
if you need to provide any VPN Client Pro logs, I'm ready
On a 4-peer configuration.
With and without the "Set the maximum number of handshake attempts before disconnecting" option.
It is enough to register arbitrary peers (IP) so that they are not available via UDP (,
and you will see that after 4 cycles of checking, the connection itself goes into the Disable status,
It is normal that the number of peers > 1, and VPN Client Pro tries to connect one by one (I have 4 entry points, some of them may be unavailable at certain times)
But when all 4 points are not available, VPN Client Pro performs 4 check cycles and goes into Disable status - opening the way for traffic without VPN
Please Help
if you need to provide any VPN Client Pro logs, I'm ready
Re: wireguard connection, if condition > 1 peer - desable after 4th cycle
Thanks for reporting the problem.
I will check and fix it...
I will check and fix it...
Re: wireguard connection, if condition > 1 peer - desable after 4th cycle
The problem should be solved in new release 1.01.49
Please update the app...
Please update the app...