mirror of
https://github.com/ProxymanApp/Proxyman.git
synced 2026-04-28 17:45:50 +03:00
[GH-ISSUE #1435] Proxyman slowing connection after running for long periods in background #1429
Labels
No labels
Discussion
Feature request
In Progress...
Plugins
Waiting response
Windows
Windows
bug
duplicate
enhancement
feature
good first issue
iOS
macOS 10.11
question
wontfix
✅ Done
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Proxyman#1429
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 @cameroncooke on GitHub (Nov 16, 2022).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1435
Originally assigned to: @NghiaTranUIT on GitHub.
Description
Occasionally when running Proxyman in the background for long periods of time network requests will take longer than usual or stop working at all. Usually, I check my network and Wifi settings but then remember that I'm running Proxyman and close Proxyman and the network comes back to normal speeds.
Is this a known issue or have their been other reports of instability when left running?
I've checked and I'm not running any throttling or anything that would cause slowness. Closing and re-opening Proxyman also fixes the issue without changing any settings which makes me think it's an issue with Proxyman.
Environment
@NghiaTranUIT commented on GitHub (Nov 16, 2022):
Can you share with me the list of SSL Proxying List (In Tool Menu -> SSL Proxying)?
If you enable SSL Proxying on Web Browsers (e.g Google Chrome, Safari, etc), it might significantly impact on the performance + Ram Usage.
@cameroncooke commented on GitHub (Nov 17, 2022):
Sure thing, next time it happens I'll grab some configuration and diagnostics. Just wanted to raise here in case it was a known issue.
@cameroncooke commented on GitHub (Nov 17, 2022):
@NghiaTranUIT so it's happened again, no traffic is appearing in Proxyman at all, though the data up/down in the status bar is showing live data usage. Web pages are not loading and just timing out with:
What would you like me to do, I'm 100% sure if I close and re-open Proxyman it will resolve the issue. If I un-tick use "Override macOS proxy" the websites load again (to be expected), when re-enabling this option traffic will not come through Proxyman.
I do have a good number of domains and patterns in SSL Proxying maybe 50 or so but not all are enabled, I also have "Chrome" app-enabled for SSL proxying.
I've tried turning off SSL proxying and even stop/start recording and it made no difference.
Let me know what I can do to help you debug, of course, if I close the app and re-open it will resolve itself so I'll leave the app running and just disable the "Override macOS proxy" in the mean time.
@NghiaTranUIT commented on GitHub (Nov 18, 2022):
It might cause a problem. By enabling the entire Google Chrome or Safari app, Proxyman will capture all HTTPS traffic and store the data in the memory. It significantly impacts performance if you listen to music on Youtube due to the enormous traffic.
Because this website has a special security mechanism to reject all self-signed certificates. It doesn't relate to the performance issue that we're discussing.
If the app is slow, I suggest clicking on the Clear Session (🗑️ icon) on the Top Tool Bar. It will wipe out all memory and might improve the responsiveness.
@cameroncooke commented on GitHub (Nov 18, 2022):
Sorry appstoreconnect was just one example to clarify when this happens no
webpages will load.
I’ve turned SSL proxying off and this does not fix the issue.
Clear session has no effect.
Turning off recording has no effect.
No traffic is recorded at all by Proxyman.
Would you like me to send you additional information to debug, please let me know what you want me to do.
@cameroncooke commented on GitHub (Nov 18, 2022):
I believe this to be a bug as I would expect Proxyman to work in the background, it works and no settings are changed and then just stops receiving or processing traffic until terminated. I'm not watching YouTube videos. Memory usage according to Proxyman 252MB that's after I cleared the session which doesn't fix the issue.
After this happened I turned off SSL Proxying.
SSL Proxying: disabled
Recording: enabled
Clear session: done
https://user-images.githubusercontent.com/630601/202668602-8ecca34b-92d7-4544-81be-105e4024faab.mov
@NghiaTranUIT commented on GitHub (Nov 19, 2022):
Thanks for the video. Not sure what causes the problem on macOS Ventura 13.1 Beta. I've tested with Ventura 13.0 but I could not reproduce it. Additionally, there is no similar report on this issue. I suppose it's related to the Beta OS.
Please help me:
If it's remained, Please download the Charles Proxy app and open it (No need to install the certificate, just run as a normal proxy) => Verify whether the issue is fixed or not.
Meanwhile, I will update my Mac Mini M1 to Ventura 13.1 Beta tonight and try to see what's happened.
@cameroncooke commented on GitHub (Nov 19, 2022):
Proxyman works fine on Ventura. The issue I’m seeing is if I leave it
running for a long time maybe all day then at some point it just stops
working as shown in the video.
Requests are timing out and Proxyman is not receiving traffic.
The fix is easy, no reset required, just close and re-open Proxyman.
I’m not looking to fix the issue as I can already do that by closing and
re-opening.
I wanted to try and help you find the cause so maybe you can fix it.
My post here wasn’t looking for solution but trying to help you.
Seems unlikely to be a Ventura issue as the fix is closing and reopening
Proxyman. Nothing has to be changed at the OS level.
On Sat, 19 Nov 2022 at 06:55, Nghia Tran @.***> wrote:
--
Cameron.
@NghiaTranUIT commented on GitHub (Nov 19, 2022):
Hey, I'm able to reproduce your issue on macOS 13.1 Beta.
The app works fine on Ventura 13.0 RC. Not the why the Beta causes the bug. I'm investigating now.
@cameroncooke commented on GitHub (Nov 19, 2022):
Ok cool. I'll close Proxyman as I've had it open for days. haha thanks.
Cameron.
On Sat, 19 Nov 2022 at 15:53, Nghia Tran @.***> wrote:
@NghiaTranUIT commented on GitHub (Nov 22, 2022):
Hey @cameroncooke let's try this beta build: https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_3.13.0_Fix_DNS_issue_on_Ventura_Beta.dmg
The problem was: on the Ventura 13.1 Beta, https://dns.google is routed to the Proxy (Other macOS or Ventura 13.0, it isn't). Sometimes, it's not reachable. It happens with Charles Proxy app too.
Fix by always ignoring the
https://dns.googleand it might fix the bug@NghiaTranUIT commented on GitHub (Nov 23, 2022):
@cameroncooke I discover why the original issue takes place. It is because, on macOS Ventura 13.1 Beta, DNS over HTTPS is enabled by default, by the system. Additionally, it doesn't work well with ipv4 Proxy Server (Proxyman).
I enabled ipv4 and ipv6 and the issue is gone 👍
Beta build: https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_3.13.0_Fix_DNS_Over_HTTPS_v2.dmg
@cameroncooke commented on GitHub (Nov 23, 2022):
Just opened the Beta build, what does this mean:
@cameroncooke commented on GitHub (Nov 23, 2022):
Closed and re-opened it again and now it seems to be working.
@NghiaTranUIT commented on GitHub (Nov 23, 2022):
I've recently encountered this issue too, there is a race-condition when starting to listen on ipv4 and ipv6 at the same time.
I'm fixing it 👍
@cameroncooke commented on GitHub (Nov 23, 2022):
Ok cool, I'm going to run the beta for the day and see how it runs.
@NghiaTranUIT commented on GitHub (Nov 24, 2022):
If you've encountered the
Core starts failed, here is the fix: https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_3.13.0_Fix_Websocket_failed.dmg 👍