ProxymanApp / ProxymanApp/Proxyman

Network traffic hangs and timeouts when proxyman left running after Mac resumes from sleep

Open
#1,726 4 comments 0 reactions 1 assignee View on GitHub

@NghiaTranUIT is already working on this.

Since Jul 29, 2023.

bug
Dominant language
No language data
Stars
7k
Forks
237
PR merge metrics
No merged PRs in 30d

Description

Description

Network traffic hangs and timeouts when Proxyman is left running after Mac resumes from sleep. This has been happening for as long as I've had Proxyman on many different versions of Proxyman and macOS versions.

Essentially if I leave the application running for a long period of time, usually overnight and wake the computer from sleep while Proxyman application is still open the network traffic stops working. Web browsers show error screens to check firewall/VPN, and other applications just timeout.

Proxytman UI shows no traffic at all, in-fact all the historic traffic disappears from the UI!

It's quite easy to fix, closing and re-opening Proxyman always fixes the issue, but of course, I've lost any historical traffic I had previously captured.

Screenshot 2023-07-28 at 09 01 14 Screenshot 2023-07-28 at 08 59 30

Steps to Reproduce

  1. Leave Proxyman running all day and overnight while MacBook sleeps
  2. Wake MacBook from sleep in the morning
  3. Observe Proxyman is still running but network traffic times out

Current Behavior

Proxtman stops collecting and processing traffic, computer network requests timeout.

Expected Behavior

Proxyman should work when resuming from long periods of sleep and use, alternatively, the application should stop overriding the macOS proxy when the Mac goes to sleep and resume after.

Environment

  • Proxyman 4.9.0
  • macOS 14.0 Beta (23A5301g)

I've also observed the same issues on Proxyman versions dating back to 1.0 and macOS versions including Ventura so I don't believe this is caused by environmental compatibility.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.