[Bug]: The connection drops after the screen has been locked for a period of time.

[laveta331-jpg]

Platform

Windows

ProxyBridge Version

4.0.0

OS and Version

Windows 11

Documentation

• I have read the Windows documentation
• I have read the macOS documentation
• I have read the Linux documentation

Code Review

• I have gone through the code page

Describe the Bug

The connection drops after the screen has been locked for a period of time, and the software must be restarted to function correctly. This issue did not exist in the previous version.
For example, if I lock the computer (without putting it to sleep) before leaving get off work, I have to restart the software the next day to get it working properly.

Additional Context

No response

[Anof-cyber]

@laveta331-jpg can you share any activity logs post-unlock?

[laveta331-jpg]

@laveta331-jpg* 能否分享一下解锁后的活动日志？

[21:58:24] [UDP RELAY] TCP control connection closed for proxy 127.0.0.1:10808 鈥?reconnecting
[21:58:24] UDP ASSOCIATE established with SOCKS5 proxy 127.0.0.1:10808 (UDP relay at 127.0.0.1:58018)
[21:58:24] [UDP RELAY ERROR] Failed to receive from proxy 127.0.0.1:10808: 10022 - closing
[21:58:25] UDP ASSOCIATE established with SOCKS5 proxy 127.0.0.1:10808 (UDP relay at 127.0.0.1:63130)
[22:03:25] [UDP RELAY] TCP control connection closed for proxy 127.0.0.1:10808 鈥?reconnecting
[22:03:25] UDP ASSOCIATE established with SOCKS5 proxy 127.0.0.1:10808 (UDP relay at 127.0.0.1:59108)
[22:08:25] [UDP RELAY] TCP control connection closed for proxy 127.0.0.1:10808 鈥?reconnecting
[22:08:25] UDP ASSOCIATE established with SOCKS5 proxy 127.0.0.1:10808 (UDP relay at 127.0.0.1:58389)
[22:08:25] [UDP RELAY ERROR] Failed to receive from proxy 127.0.0.1:10808: 10022 - closing
[22:08:26] UDP ASSOCIATE established with SOCKS5 proxy 127.0.0.1:10808 (UDP relay at 127.0.0.1:58390)
[22:13:26] [UDP RELAY] TCP control connection closed for proxy 127.0.0.1:10808 鈥?reconnecting
[22:13:26] UDP ASSOCIATE established with SOCKS5 proxy 127.0.0.1:10808 (UDP relay at 127.0.0.1:52128)
[22:13:26] [UDP RELAY ERROR] Failed to receive from proxy 127.0.0.1:10808: 10022 - closing
[22:13:27] UDP ASSOCIATE established with SOCKS5 proxy 127.0.0.1:10808 (UDP relay at 127.0.0.1:52129)
[22:18:27] [UDP RELAY] TCP control connection closed for proxy 127.0.0.1:10808 鈥?reconnecting
[22:18:27] UDP ASSOCIATE established with SOCKS5 proxy 127.0.0.1:10808 (UDP relay at 127.0.0.1:51556)
[22:23:27] [UDP RELAY] TCP control connection closed for proxy 127.0.0.1:10808 鈥?reconnecting
[22:23:27] UDP ASSOCIATE established with SOCKS5 proxy 127.0.0.1:10808 (UDP relay at 127.0.0.1:56860)
[22:28:27] [UDP RELAY] TCP control connection closed for proxy 127.0.0.1:10808 鈥?reconnecting
[22:28:27] UDP ASSOCIATE established with SOCKS5 proxy 127.0.0.1:10808 (UDP relay at 127.0.0.1:49412)
[22:28:27] [UDP RELAY ERROR] Failed to receive from proxy 127.0.0.1:10808: 10022 - closing
[22:28:28] UDP ASSOCIATE established with SOCKS5 proxy 127.0.0.1:10808 (UDP relay at 127.0.0.1:49413)

The other logs have been overwritten; only this one remains.

[buffcow]

Same here. +1

[WvvvWv]

Same here—+1. I've temporarily switched back to the old version 3.2.

[hulisang]

我也有这个问题，电脑长时间空闲之后就必须重启ProxyBridge才能使用

[Anof-cyber]

Could you provide some details? Is the issue related to manual screen lock after a few minutes based on your system settings, where unlocking doesn't work? Or is it specific to Windows sleep mode

? Please verify if this behaviour occurs only during auto sleep/lock or also when you manually lock or put the system to sleep.

The app itself has no control over timeout, lock, or similar settings; it solely depends on your Windows power and performance configurations.

I tested the same scenarios in lock and sleep mode, and after unlocking, everything works fine. Could the proxy server be causing the issue? Post-unlock, the proxy server might be stopped or need a restart instead of using proxybridge. Also, can you check if you are experiencing issues with TCP, UDP, or both?

[buffcow]

Could you provide some details? Is the issue related to manual screen lock after a few minutes based on your system settings, where unlocking doesn't work? Or is it specific to Windows sleep mode

? Please verify if this behaviour occurs only during auto sleep/lock or also when you manually lock or put the system to sleep.

The app itself has no control over timeout, lock, or similar settings; it solely depends on your Windows power and performance configurations.

I tested the same scenarios in lock and sleep mode, and after unlocking, everything works fine. Could the proxy server be causing the issue? Post-unlock, the proxy server might be stopped or need a restart instead of using proxybridge. Also, can you check if you are experiencing issues with TCP, UDP, or both?

It might not be caused by locking the screen or entering sleep mode; perhaps it just happens after running for a long time?

However, I happened to encounter this exact issue, as shown in the video.

I took a lunch break and kept the screen locked for about an hour; everything was fine after unlocking it, but the issue appeared after I switched proxy nodes in my proxy software. I suspect it’s the same problem as the one in this issue.

！！I am quite certain that the proxy I used before and after switching were both fine.

ProxyBridgeIssue.mp4.gz

[WvvvWv]

能否提供一些详细信息？这个问题是否与系统设置中几分钟后手动锁定屏幕且无法解锁有关？还是仅限于 Windows 睡眠模式？
请确认此现象是否仅在自动睡眠/锁定期间出现，还是在手动锁定或使系统进入睡眠状态时也会出现。
该应用程序本身无法控制超时、锁定或类似设置；它完全取决于您的 Windows 电源和性能配置。
我在锁定和睡眠模式下测试了相同的场景，解锁后一切正常。代理服务器会不会是问题所在？解锁后，代理服务器可能停止运行或需要重启，而不是使用代理桥接。另外，您能否检查一下您遇到的问题是 TCP、UDP 还是两者都存在？

这可能并非由锁定屏幕或进入睡眠模式引起；或许只是在长时间运行后才会发生？

然而，我恰好遇到了视频中所示的这个问题。

我午休的时候屏幕锁住了大约一个小时；解锁后一切正常，但切换代理软件中的代理节点后问题就出现了。我怀疑这和这个问题一样。

ProxyBridgeIssue.mp4.gz

Yes, I also don't think it was caused by sleep mode; the disconnection happened simply after unlocking the computer. Also, I have all my rules set to "BOTH." The issue hasn't occurred since I reverted to version 3.2.

[Anof-cyber]

@WvvvWv can you test with tcp only rules? as UDP might be the culprit as it has lot of things i am only able to verify for TCP as i dont have UDP setup available at the moment.

[buffcow]

@WvvvWv can you test with tcp only rules? as UDP might be the culprit as it has lot of things i am only able to verify for TCP as i dont have UDP setup available at the moment.

I only configured TCP, but this issue still occurs.

[Anof-cyber]

I am not able to verify what the culprit, i am not able to see any of this on my sysyme. Probably not related to this; can you let me know your Windows power settings? Also, is it a desktop or a laptop?

The app itself has no control over this its a windows who control what will activity on the kernel and network will run in lock or sleep mode.