[GH-ISSUE #1660] Connection is reset when clicking the "clear entire session" button #1652

Closed
opened 2026-03-03 19:53:12 +03:00 by kerem · 6 comments
Owner

Originally created by @seidnerj on GitHub (Jun 1, 2023).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1660

Description

Connection is reset when clicking the "clear entire session" button

Steps to Reproduce

  1. Run an ongoing process that's tunneled through ProxyMan
  2. Press the clear entire session button

Current Behavior

Depending on the software you're running you'll get a different error message but they will also essentially say the connection was reset, e.g.:

raise ProxyError(e, request=request)
requests.exceptions.ProxyError: MyHTTPSConnectionPool(host='domain.com', port=443): Max retries exceeded with url: ...

Expected Behavior

Connection should not be reset

Environment

  • App version: Proxyman 4.8.0
  • macOS version: macOS Ventura v13.4
Originally created by @seidnerj on GitHub (Jun 1, 2023). Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1660 ## Description Connection is reset when clicking the "clear entire session" button ## Steps to Reproduce 1. Run an ongoing process that's tunneled through ProxyMan 2. Press the clear entire session button ## Current Behavior Depending on the software you're running you'll get a different error message but they will also essentially say the connection was reset, e.g.: raise ProxyError(e, request=request) requests.exceptions.ProxyError: MyHTTPSConnectionPool(host='domain.com', port=443): Max retries exceeded with url: ... ## Expected Behavior Connection should not be reset ## Environment - App version: Proxyman 4.8.0 - macOS version: macOS Ventura v13.4
kerem 2026-03-03 19:53:12 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@NghiaTranUIT commented on GitHub (Jun 2, 2023):

Yes, it's expected behavior. Clearing the session means closing all alive connections and wiping out the app memory.

If you'd like to ignore this domain from the app -> You can add it in the Bypass Proxy List in the Tools Menu -> SSL Proxying List.

<!-- gh-comment-id:1573007634 --> @NghiaTranUIT commented on GitHub (Jun 2, 2023): Yes, it's expected behavior. Clearing the session means closing all alive connections and wiping out the app memory. If you'd like to ignore this domain from the app -> You can add it in the Bypass Proxy List in the Tools Menu -> SSL Proxying List.
Author
Owner

@seidnerj commented on GitHub (Jun 2, 2023):

Okay, how about if I just want to clear everything in ProxyMan'a interface, ui-wise, without resetting connections? Is it possible to so somehow?

Many times when I start a new debugging session or during one, I want to delete everything that I've already captured so I so its easier to tell what happened starting from "now" (the moment where I clear the data")

<!-- gh-comment-id:1573237663 --> @seidnerj commented on GitHub (Jun 2, 2023): Okay, how about if I just want to clear everything in ProxyMan'a interface, ui-wise, without resetting connections? Is it possible to so somehow? Many times when I start a new debugging session or during one, I want to delete everything that I've already captured so I so its easier to tell what happened starting from "now" (the moment where I clear the data")
Author
Owner

@NghiaTranUIT commented on GitHub (Jun 2, 2023):

Unfortunately, it's not possible for now. The only way is using the By-Pass Proxy list, so this domain never hits Proxyman.

Even though you're using Block List with "Hide, but not block" Option, "Clear Session" will close all connections.

<!-- gh-comment-id:1573239839 --> @NghiaTranUIT commented on GitHub (Jun 2, 2023): Unfortunately, it's not possible for now. The only way is using the By-Pass Proxy list, so this domain never hits Proxyman. Even though you're using Block List with "Hide, but not block" Option, "Clear Session" will close all connections.
Author
Owner

@seidnerj commented on GitHub (Jun 2, 2023):

Okay got it. Closing this for now. Thanks!

<!-- gh-comment-id:1573240458 --> @seidnerj commented on GitHub (Jun 2, 2023): Okay got it. Closing this for now. Thanks!
Author
Owner

@mjnguyen commented on GitHub (Jul 14, 2025):

@NghiaTranUIT: has there been a change on this stance? it's one feature CharlesProxy has I find very useful to debug active connections by clearing all completed requests. bypassing is too cumbersome and specific.

Thanks!

<!-- gh-comment-id:3070319995 --> @mjnguyen commented on GitHub (Jul 14, 2025): @NghiaTranUIT: has there been a change on this stance? it's one feature CharlesProxy has I find very useful to debug active connections by clearing all completed requests. bypassing is too cumbersome and specific. Thanks!
Author
Owner

@NghiaTranUIT commented on GitHub (Jul 15, 2025):

not yet, to make it simple, we decide to reset all active connections, so it can take effect if we have new active debugging tools.

May I ask what problem it causes? @mjnguyen

<!-- gh-comment-id:3071570939 --> @NghiaTranUIT commented on GitHub (Jul 15, 2025): not yet, to make it simple, we decide to reset all active connections, so it can take effect if we have new active debugging tools. May I ask what problem it causes? @mjnguyen
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Proxyman#1652
No description provided.