You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
in the VPN mode the program starts writing “connection” instead of “connected” after a minute of work. the button is lit yellow. the only way to return it to the “connected” state is to click on the place where the test URL delay should be written. this is enough for a minute, after that the problem repeats. the problem does not occur in the “system proxy” mode. the window is open or minimized - it does not matter. VPN works in "connection" state but looks kinda scary :D
Minimal Reproducible Example (MRE)
open the application
Select the “VPN (experimental)” operating mode
Connect to the VLESS configuration
Wait one minute
See that the program has entered the “Connect” state
Expected Behavior
No response
Version
v2.5.7
Platform/OS
Windows
Additional Context
No response
Application Config Options
No response
Relevant log output
No response
Are you willing to submit a PR? If you know how to fix the bug.
I'm willing to submit a PR (Thank you!)
The text was updated successfully, but these errors were encountered:
Search first
What Happened?
in the VPN mode the program starts writing “connection” instead of “connected” after a minute of work. the button is lit yellow. the only way to return it to the “connected” state is to click on the place where the test URL delay should be written. this is enough for a minute, after that the problem repeats. the problem does not occur in the “system proxy” mode. the window is open or minimized - it does not matter. VPN works in "connection" state but looks kinda scary :D
Minimal Reproducible Example (MRE)
Expected Behavior
No response
Version
v2.5.7
Platform/OS
Windows
Additional Context
No response
Application Config Options
No response
Relevant log output
No response
Are you willing to submit a PR? If you know how to fix the bug.
The text was updated successfully, but these errors were encountered: