Viscosity does not follow 'pick next remote' notification from the server

Got a problem with Viscosity or need help? Ask here!


Posts: 1
Joined: Wed Jun 03, 2020 8:28 am

Post by aivanise » Wed Jun 03, 2020 8:39 am
When an UDP based server that has the 'explicit-exit-notify 2' option restarts, it sends a flag to the connected clients that they have to pick another remote. This can be simulated by sending 'client-kill cid RESTART,[N]' from the management interface.

This does not happen in Viscosity, both 1.8.5 and 1.8.6 latest beta do not follow a restart signal from the server to skip to the next remote and stick to whatever is resolved first.

In my case remote is specified as a DNS round robin entry with multiple IPs. No matter what flag is sent by the server, Viscosity sticks to the first resolved IP, unless it is not available. That makes rebalancing or evacuating the servers before maintenance very user unfriendly.

homebrew version of openvpn 2.4.9 behaves correctly.


User avatar
Posts: 1978
Joined: Thu Sep 04, 2008 9:27 pm

Post by James » Wed Jun 03, 2020 1:02 pm
Hi aivanise,

Thanks for the report - we'll look into it and fix up the behaviour in the next beta release if needed.

James Bekkema
Viscosity Developer

2 posts Page 1 of 1