Win10 enterprise latest updates, normally use Cisco AnyConnect for VPN connection (so it is installed on my computer)
Same problem here with 1.2.8 and 1.2.10. Previous Tap client works (eg 1.1.2 ?)
Indeed, v 1.1.2 was the ONLY version that ever worked as intended on my PC.... All other versions, though the app actually confirmed to have established a secure connection, failed to do so - again easily tested for browser traffic via any website that shows one's external IP address....
@mookrhodan Thanks for trying Outline. Sorry you've been having trouble with the new Windows client. Can you please paste the output of route print? That will help me see why Outline cannot connect.
BTW, yes, you're right the uninstaller does not remove the TAP device (it is possible to do it manually) but can you clarify what you mean by "nor does it remove VPN server settings from computer during uninstall"?
@seanxushen FYI, 1.1.2 did not include the TAP driver. Again, if you can paste the output of route print it will help us see what's going wrong.
@trevj
I'm also having this issue, here's the output of my route print (I uploaded it to my google cloud storage bucket because it seemed too big to copy/paste into here).
I don't have any other VPN software installed, only Outline. This has been happening even with the v1.2.11 Windows pre-release. I'm on Windows 10 Home, 64-bit if that helps.
@xDrixxyz Thanks for the report. I can see you have VMWare installed. We have not tested cooperation with virtualisation/emulation software extensively.
One question for now:
@mookrhodan
BTW, if you'd prefer, there are several alternative ways to contact the team - all listed in the app.
@trevj Nope, Outline installed successfully and without errors.
@xDrixxyz OK, thanks. I'm afraid I'll need a little more info in order to debug this. Can I please ask you to submit feedback using the app?:
This sends us a little more info on your network devices than is contained in route print.
Thanks again!
@xDrixxyz Many thanks. This tells me the error isn't, in fact, related to VMWare. Instead, you have multiple network devices with gateways. I'm still not sure how that happens but I'm going to prioritise a fix that guesses which one is "really" active by examining the device metric.
@mookrhodan @xDrixxyz I just merged https://github.com/Jigsaw-Code/outline-client/pull/281 which I think will help reduce unnecessary "another VPN is active" error messages. It will be in https://github.com/Jigsaw-Code/outline-client/releases/tag/windows-v1.2.12 which should go live later today. Many thanks again for helping us improve this tricky part of Outline.
It seems v1.2.13 has the same problem. I'm continuing to see the "another VPN is active" error. Win10 Pro system; WiTopia client installed, but not active.
So, as of 1.2.13 the client ignores inactive interfaces when searching for the system's IPv4 gateway, hopefully reducing the frequency of "another vpn is active" (this was a followup to 1.2.12's improvement to ignore IPv6 devices when searching for the gateway). One remaining improvement is when we find multiple devices with IPv4 gateways to choose the device with the lowest metric.
@seanxushen @xDrixxyz Please try connecting with 1.2.13. I hope it addresses your issue.
@wkwalker Sorry you're having problems with Outline. If you could please follow the steps above to send us detailed info on your system's network devices then I may be able to tell whether the remaining improvement I mentioned earlier will help you:
https://github.com/Jigsaw-Code/outline-client/issues/262#issuecomment-422172358
Yes, I can successfully connect to my Outline Server now. Thank you @trevj !
@xDrixxyz Delighted to hear it!
Closing this due to inactivity. All, please re-open if you continue to experience this.
Same problem here. v1.2.26, Windows 10 1903 build 18329.1.
Edit: It's working after disable Hyper-V Virtual Network Adapters.
I've continued to have the same issue since after 1.1.2 and it is still occurring with 1.2.26. Windows 10, 1803, build 17134.523.
FWIW, I have the WiTopia VPN package installed, but not active.
@mookrhodan @seanxushen @xDrixxyz @wkwalker @NoobTW I just released Windows client 1.2.29 which should help with this issue. If you still run into problems after updating please re-open. Thanks for reporting this issue!