Your client updates automatically; run zorven update to update manually. The CLI and the desktop app ship with the same version number. The macOS desktop app is also updated to 0.3.7 (from 0.3.2, including all desktop improvements since then).
Fixed
Clients 0.3.4 - 0.3.6 could get stuck after a disconnect when the failover node list sent by the server contained an IP address. The log showed cannot validate certificate for ... because it doesn't contain any IP SANs and the client stayed "not connected".
- Server side (live): the node list now contains only the public address clients can reach (
zorven.app:443). - Client 0.3.7: a failed node no longer returns to the top of the list when the retry delay grows; if every address fails they are tried in turn. IP-address node hints are ignored when your server address is a host name.
If you are stuck
A client that cannot connect cannot update itself; fix it once by hand:
- Linux (root):
rm -f /etc/zorven/nodes.json /root/.config/zorven/nodes.json && zorven service restart - Windows (administrator):
Remove-Item -Force C:\ProgramData\zorven\nodes.json -ErrorAction SilentlyContinue; zorven service restart
Then run zorven update to move to 0.3.7.