Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sudden complete uncontrolled shutdown of windscribe firewall during full traffic expiration #205

Open
winfuibe opened this issue Dec 20, 2024 · 1 comment

Comments

@winfuibe
Copy link

Describe the bug
I'm using windscribe. I use split tunneling. I've enabled windscribe in autostart and auto-connect. Windscribe is running out of traffic. Windscribe client WITHOUT any acknowledgement, WITHOUT ANY WARNING, WITHIN disconnects from vpn and WITHIN!!!!!!. FULL!!!!! FULL!!!!!!!!!!!!! DISCONNECT VPN Firewall!!!!!!!!
All open sites that should not have seen my ip see it.
My ISP, which is not supposed to see what sites I am connected to, sees and logs all the sites that were open in my browser at that moment.
I have absolutely no control over my data and my attempt at privacy for which I spent so many resources and time disappears without a trace and was meaningless all this time, because all the sites open in my browser from which I hid my IP for years now know my real IP, and have forever linked it to my accounts and all the accounts that are linked to them. If I live in a not-so-free country, I might get prosecuted or fined.

Thanks Windscribe.

OS and app information:

  • OS Windows 10 22H2 (clean build install)
  • App version v2.12.7

To Reproduce
Steps to reproduce the behavior:

  1. Wait for the end of the traffic packet
  2. Firewall is disabled on its own, without confirmation, which should NEVER be disabled on its own

Expected behavior
Disconnect from the VPN server but firewall which should be enabled, and notification from the app itself (many people disable all standard windows notifications as they come too often, annoying and useless 99.9% of the time). The user should then be able to close the browser/essential applications, and disable the firewall, realizing what has happened

@bernerdad
Copy link
Collaborator

Hi, and thank you for karenporting this issue to us. This is indeed a regression and will be fixed in a forthcoming release. And in a shameless end-of-year plug, have you considered rewarding yourself with a pro account? It costs less than a pint of beer a month, and no more getting cut off by a data cap.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants