mirror of
https://github.com/ProxymanApp/proxyman-windows-linux.git
synced 2026-04-27 00:45:55 +03:00
[GH-ISSUE #530] Intermittent failure to restore system proxy on quit #527
Labels
No labels
Linux
bug
enhancement
enhancement
pull-request
question
✅ Done
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/proxyman-windows-linux#527
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @aa1134665908 on GitHub (Aug 11, 2025).
Original GitHub issue: https://github.com/ProxymanApp/proxyman-windows-linux/issues/530
Originally assigned to: @kics223w1 on GitHub.
Description
When closing Proxyman, the application sometimes quits immediately without showing the configured confirmation dialog ("Show confirmation dialog before quitting"). This results in the system proxy settings not being reverted, which causes network connectivity issues as the system still tries to route traffic through the defunct proxy.
Steps to Reproduce
Current Behavior
Occasionally, the application closes instantly without displaying the quit confirmation prompt. The system's proxy settings are left pointing to Proxyman's proxy address, which is no longer running. This breaks all internet access until the system proxy is manually reset in the OS settings.
Expected Behavior
When attempting to close the application, the confirmation dialog should always be displayed as per the settings. After confirming the action in the dialog, Proxyman should properly revert the system proxy settings to their original state before exiting completely.
Environment
@kics223w1 commented on GitHub (Aug 11, 2025):
Hi @aa1134665908, Proxyman always reverts the proxy when it closes. The confirmation dialog does not matter for this use case.
I haven’t been able to reproduce this issue successfully, but I’ll double-check the code again 👍🏻