The daemon sub-process seems to stays alive after the VPN is stopped under some unclear circumstances (like an app update). A new daemon refuses to start as the port isn't freed.
A workaround would be to try killing any remnant daemon before starting a new one.
The daemon sub-process seems to stays alive after the VPN is stopped under some unclear circumstances (like an app update). A new daemon refuses to start as the port isn't freed.
A workaround would be to try killing any remnant daemon before starting a new one.