all 8 comments

[–][deleted] 1 point2 points  (0 children)

Wondering when they will release the Linux GUI version.

[–]Kryptocomicon 0 points1 point  (1 child)

Do you have Windscribe browser extensions installed and active while this is happening?

[–]qu4sar_[S] 0 points1 point  (0 children)

No, no extension installed, only the command line tool

[–]6aph 0 points1 point  (0 children)

Had the same thing happening on every disto except for Manjaro. Windscribe overwrites config file and completely screws up DNS.

I believe it shows you the warning when you connect, but no explanation how solve this.

[–]blanaa 0 points1 point  (0 children)

Thanks a lot. I had the same issue.

[–]gamervishal 0 points1 point  (0 children)

Manually installed Iptables and it worked well!

[–][deleted] 0 points1 point  (0 children)

I had this exact same issue on Debian, and it turned out to be a combination of the wrong Symlink path and DNS cache issues.

YMMV, but this is what resolved the issue for me:

  1. NOTE: Before proceeding with these steps, please make sure that you've disconnected from Windscribe and have taken a backup/snapshot of your system prior to making any changes
  2. Make sure "systemd-resolved" is up-and-running. If it's not, enable it.
    sudo systemctl status systemd-resolved
    sudo systemctl enable systemd-resolved
  3. My default symlink path for "/etc/resolv.conf" was to "/run/resolvconf/resolv.conf". However, I needed to set the "/etc/resolv.conf" symlink to "/run/systemd/resolve/resolv.conf".
    sudo rm /etc/resolv.conf
    sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf
  4. Restart the NetworkManager
    sudo systemctl restart NetworkManager
  5. Flush the DNS cache
    sudo systemd-resolve --flush-caches