Windscribe keeps trying to connect forever after PC wakes up

[MarkChrisE2091]

Describe the bug
Windscribe keeps hanging on connection forever without connecting after PC (Windows 10 22H2) went to sleep and wake up. And the Windscribe firewall keeps on even after trying to turn off connection.

OS and app information:

• OS: Windows 10 22H2
• App version: v2.20.7

To Reproduce
Steps to reproduce the behavior:

1. Connect Windscribe to a location.
2. Put PC (Windows 10 22H2) into sleep.
3. Wake it up.

Expected behavior
Expect internet disconnected and windscribe trying to connect to a location (setting: auto-connect), and trying forever.

Debug log or username
Log is sent via the app.

Screenshots

Additional context
It seems to be happening in recent update.

[bernerdad]

If you are not located in a censored location, we suggest turning the Circumvent Censorship feature off. Does this also occur if you use WireGuard instead of IKEv2?

[MarkChrisE2091]

No, not in a censored location at all. Just tested, same result whether Circumvent Censorship feature on or off.

When using WireGuard, the problem disappears.

Should I close the issue now?

[bernerdad]

If you are willing, could you try the 2.21.5 release with IKEv2 and let us know if this issue still occurs? Afterwards, you can then reinstall 2.20.7 if you'd rather stay on the release channel build.

[MarkChrisE2091]

I haven't tried 2.21.5 release yet. Here is a new error for WireGuard for v2.20.7.

[bernerdad]

Yes, that has been a sporadic and challenging one for us to resolve. This occurs in the WireGuard code, typically when the PC sleeps and then wakes shortly after sleeping. Do you see this consistently on PC wake, or is it sporadic for you as well?

[MarkChrisE2091]

it is quite consistent, predictable and immediate in my PC. I just have to kill the App and restart it every time.

BTW, what is unstable in v2.21.5-alpha comparing to v2.20.7?

[bernerdad]

Hi. We just released the v2.21.6 beta, which is a release candidate build, if you want to try it out. This release candidate will morph into the stable build if no issues are encountered during beta testing.

Since you are able to reproduce the WireGuard issue consistently, and we are not, could you do the following?

1. Download our log viewer utility. You can place this utility exe in whichever folder you prefer, as it is a standalone exe (e.g. does not require an installation phase). It will collect all the logs and ensure no information is missed. The submit log feature in the app may strip out some log information if the logs are large.
2. Install the 2.21.6 beta build linked above.
3. Reproduce this WireGuard issue using 2.21.6.
4. Right after reproducing the issue, run the log viewer utility and click the 'Export all logs to a 7-zip archive' button in the toolbar.
5. Share the 7-zip file with us via our file sharing service. Share it using a password, and email me the password (jonathan@our.domain.name).

Thanks!

[MarkChrisE2091]

Hi,
I installed the v2.21.5 the other day. It seems to fix the v2.20.7 problem for IKE v2.
and Yes, the wireguard issue still persist.

btw, will the log tool include any perosnal information?

[MarkChrisE2091]

also is this the exact email? or should I change the domain part? jonathan@our.domain.name

[ltguillaume]

Change the domain name 🙂

[MarkChrisE2091]

Just wanna be sure, so it will be J---@windscribe.com i am guessing?

btw, will the log tool include any perosnal information?

[ltguillaume]

btw, will the log tool include any perosnal information?

Yeah, imho. You should definitely look through it. See #257 (comment)

[bernerdad]

Apologies, I was AFK for a long weekend break. I've received the logs and will review them asap.

[bernerdad]

A few things I've noted so far after a quick review of the logs:

• You have Circumvent Censorship enabled. As mentioned ^, only use this if you are in a censored location and none of the standard protocols will connect. Using this will cause WireGuard to be drastically slower. Both the connection setup time and packet throughput once connected are much faster with this setting off.
• It looks like you have Tailscale installed. It will conflict with the Windscribe app if it is active at the same time.

[MarkChrisE2091]

I tried, even Circumvent Censorship is off. It doesn't prevent WireGuard error going away.
Tailscale is normally quited and split tunnel is set up.