Closing or disconnecting Windscribe blocks all internet access, even with its kill switch (Firewall) off.

[Koladweep]

Describe the bug
A clear and concise description of what the bug is.
An effect similar to Kill switch is achieved without enabling it when I terminate the VPN from taskbar badge icon. Note that the Windscribe Firewall is disabled and I am only using the VPN for a few handpicked applications.

OS and app information:

• OS: Debian 12 (Bookworm), kernel version 6.1.0-40-amd64
• App version v2.17.9

To Reproduce
Steps to reproduce the behavior:

1. Connect to the internet and verify internet access.
2. launch Windscribe VPN client
3. Enable split tunnelling in inclusive mode and add all the apps you want to use Windscribe for.
4. Make sure that Windscribe Firewall is disabled.
5. Connect to the VPN (let the Windscribe client select the best option from available servers)
6. Test the apps for connectivity. (should work if your connection is sound)
7. Terminate Windscribe using taskbar Windscribe icon or, disconnect using Windscribe App interface.
8. All internet connections accross the system fail (Try to ping any website or remote server using terminal - It fails to resolve. Only devices connected to the local network can be pinged.)
9. Reboot the computer. All connections work as expected without having to connect to VPN.

Expected behaviour
Regular internet connectivity after disconnecting or terminating the Windscribe VPN client.

Debug log or username
windscribe_debug_log.txt

Additional context
Does this bug occur in previous versions of the app or is it new to the build version you noted above?

I have been experiencing this issue for a few versions so far- the only hiccup I've had with this app. This also appears to be related to the closed issues #241 and #264.

[Ivantheallknowing]

I noticed that you're using tailscale as well. Does the same happen if you disconnect tailscale first, before connecting to Windscribe?

[Koladweep]

I noticed that you're using tailscale as well. Does the same happen if you disconnect tailscale first, before connecting to Windscribe?

The same issue persists with tailscaled turned off.

[Ivantheallknowing]

Could you provide the output for sudo iptables -L -v -n while you're disconnected. And the app debug log right after you disconnect.

[Koladweep]

I must apologise for the delay in my response. Here are the logs.

If the information is of any help, I discovered a quick fix.
Every time I disconnect the VPN client, the trouble with regular connections takes place. Disconnecting and reconnecting to the WLAN fixes the issue.

iptables -L -v -n.txt

windscribe_debug_log.txt

[Ivantheallknowing]

@Koladweep I see UFW entries as well in the IPTables rules. Could you disable UFW and see if the same thing happens still?

[Koladweep]

@Koladweep I see UFW entries as well in the IPTables rules. Could you disable UFW and see if the same thing happens still?

Yes. Exactly the same thing happens even if I disable UFW. Fix also remains the same- resetting the internet connection.

iptables -L -v -n.txt
windscribe_debug_log.txt

[brentlr]

I have the exact SAME issue using the following
Cachy OS 6.17.8-2-cachyos (64-bit)
App Version 2.8.15
I have tried all of the above and my fix is the same with UFW off or On and I am trying to be kind to Windscibe's network by using Split Tunneling for streaming. Gary thought it was a problem with System d but I tried his recommendations and they do not work ether. Please let us know when fixed, Thank you for your help!

[brentlr]

Is there a cmd to add to Windscribe to force the KILL SWITCH off that we could add somewhere in Windscirbe for the interim? Like a Post command? Thank You

[jaxu]

Sorry, this one has been lingering a bit as we have been focused on other tasks.

Neither our QA nor devs are able to reproduce this one on fresh installs of Debian or CachyOS.

The original report indicates that LAN addresses are still accessible, which makes me think this is not a firewall issue at all but a DNS issue. Do you have anything else managing your DNS? What does resolvectl dns tell you before, during and after VPN connection?

Can you change Preferences => Advanced Options => DNS Manager to "resolvectl" instead of Auto and see if that makes any difference?

[brentlr]

Hi and Thank you Jason for looking into this, I saw another guy that is having same issue with an earlier WS client in Git HUB Forum. I do not have resolvectl but I do have an option of resolveconf so I assume that is what I will use and send you back the result after I reboot, etc. I want Split Tunneling to work so I can use Librewolf as an excluded app to stream music I also have added spotify as app. This way I minimize impact on streaming junk thru the Windscribe Network!!! We should write a tip on Split Tunneling and use this as an example to post for other users, I think it would save Bandwidth big time once users understand how to set it up in an Easy to understand step by step Doc or Article. I am sure that Yagar would approve and like the idea! Let me check now and I will send you my results using the above settings. Thank You 🫠

…

On Wed, Nov 19, 2025 at 12:59 PM Jason Xu ***@***.***> wrote: *jaxu* left a comment (Windscribe/Desktop-App#266) <#266 (comment)> Sorry, this one has been lingering a bit as we have been focused on other tasks. Neither our QA nor devs are able to reproduce this one on fresh installs of Debian or CachyOS. The original report indicates that LAN addresses are still accessible, which makes me think this is not a firewall issue at all but a DNS issue. Do you have anything else managing your DNS? What does resolvectl dns tell you before, during and after VPN connection? Can you change Preferences => Advanced Options => DNS Manager to "resolvectl" instead of Auto and see if that makes any difference? — Reply to this email directly, view it on GitHub <#266 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BCKIPR5ALKCI35HBQSWQWRT35SVZDAVCNFSM6AAAAACIDXM3AKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKNJTHE4TCOBZGI> . You are receiving this because you commented.Message ID: ***@***.***>

[Koladweep]

Hey! I have an update. I don't know what fixed it- any recent update or the fix I am going to mention. I am using Tailscale and it has a feature I recently discovered to be conflicting with other applications. I turned off MagicDNS- a very minor inconvenience and that conflict was resolved. I recently used Windscribe VPN and found that the problem #266 did not occur. I tried enabling MagicDNS and the issue #266 still does not occur on my system. For me it seems to have vanished.

windscribe_log_29-11-2025_2005.txt