[GH-ISSUE #1928] Proxyman Causes Massive Request Load #1921

Open
opened 2026-03-03 19:55:27 +03:00 by kerem · 18 comments
Owner

Originally created by @hcarstensen on GitHub (Feb 7, 2024).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1928

Originally assigned to: @NghiaTranUIT on GitHub.

Description

In certain situations Proxyman causes a massive IO/CPU load repeating the same request over and over again.
In my case this is triggered by the ESET AntiVirus Tool when checking for updated signatures.
See attached Screenshot for details.

Steps to Reproduce

  1. Install ESET AntiVirus
  2. Start Proxyman
  3. Open ESEt AntiVirus and check for signature updates

Current Behavior

Proxyman repeats a HEAD request over and over again causing high IO/CPU load.

Expected Behaviour

Proxyman executes the request once.

Environment

  • App version: e.g Proxyman 4.16.0
  • macOS version: macOS Sonoma 14.3

Proxyman

Originally created by @hcarstensen on GitHub (Feb 7, 2024). Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1928 Originally assigned to: @NghiaTranUIT on GitHub. ## Description In certain situations Proxyman causes a massive IO/CPU load repeating the same request over and over again. In my case this is triggered by the ESET AntiVirus Tool when checking for updated signatures. See attached Screenshot for details. ## Steps to Reproduce <!-- Add relevant code and/or a live example --> 1. Install ESET AntiVirus 2. Start Proxyman 3. Open ESEt AntiVirus and check for signature updates ## Current Behavior Proxyman repeats a HEAD request over and over again causing high IO/CPU load. ## Expected Behaviour Proxyman executes the request once. ## Environment - App version: e.g Proxyman 4.16.0 - macOS version: macOS Sonoma 14.3 ![Proxyman](https://github.com/ProxymanApp/Proxyman/assets/24648317/6a4f1169-4de3-4775-9f50-b3aa681cf0c8)
Author
Owner

@NghiaTranUIT commented on GitHub (Feb 7, 2024):

It seems that ESET AntiVirus Tool conflicts with Proxyman app.

You can fix it by open the Tools menu -> Proxy Setting -> Bypass Proxy Setting -> Add update.eset.com to the list (separate by the comma). This will make the Virus checker never go to the Proxyman app.

<!-- gh-comment-id:1931899270 --> @NghiaTranUIT commented on GitHub (Feb 7, 2024): It seems that ESET AntiVirus Tool conflicts with Proxyman app. You can fix it by open the Tools menu -> Proxy Setting -> Bypass Proxy Setting -> Add `update.eset.com` to the list (separate by the comma). This will make the Virus checker never go to the Proxyman app.
Author
Owner

@hcarstensen commented on GitHub (Feb 7, 2024):

Hi!

I already tried this but unfortunately it does not fix my problem.
Here is my list of bypasses:

dns.google,one.one.one.one,ocsp.digicert.com,update.eset.com

Am 07.02.2024 um 13:00 schrieb Nghia Tran (Noah) @.***>:

It seems that ESET AntiVirus Tool conflicts with Proxyman app.

You can fix it by open the Tools menu -> Proxy Setting -> Bypass Proxy Setting -> Add update.eset.com to the list (separate by the comma). This will make the Virus checker never go to the Proxyman app.


Reply to this email directly, view it on GitHub https://github.com/ProxymanApp/Proxyman/issues/1928#issuecomment-1931899270, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF4BU7LZNDYALCQ5KMR2Q6TYSNUGLAVCNFSM6AAAAABC5V45OCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZRHA4TSMRXGA.
You are receiving this because you authored the thread.

<!-- gh-comment-id:1931914060 --> @hcarstensen commented on GitHub (Feb 7, 2024): Hi! I already tried this but unfortunately it does not fix my problem. Here is my list of bypasses: dns.google,one.one.one.one,ocsp.digicert.com,update.eset.com > Am 07.02.2024 um 13:00 schrieb Nghia Tran (Noah) ***@***.***>: > > > It seems that ESET AntiVirus Tool conflicts with Proxyman app. > > You can fix it by open the Tools menu -> Proxy Setting -> Bypass Proxy Setting -> Add update.eset.com to the list (separate by the comma). This will make the Virus checker never go to the Proxyman app. > > — > Reply to this email directly, view it on GitHub <https://github.com/ProxymanApp/Proxyman/issues/1928#issuecomment-1931899270>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AF4BU7LZNDYALCQ5KMR2Q6TYSNUGLAVCNFSM6AAAAABC5V45OCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZRHA4TSMRXGA>. > You are receiving this because you authored the thread. >
Author
Owner

@NghiaTranUIT commented on GitHub (Feb 7, 2024):

Is it possible to add Proxyman in the Exception List of the Anti Virus? So fix the issue 🤔

Or try to turn off the anti-virus temporarily,

<!-- gh-comment-id:1931918503 --> @NghiaTranUIT commented on GitHub (Feb 7, 2024): Is it possible to add Proxyman in the Exception List of the Anti Virus? So fix the issue 🤔 Or try to turn off the anti-virus temporarily,
Author
Owner

@hcarstensen commented on GitHub (Feb 7, 2024):

Update: Just had another request load being triggerd by some Google services. See Screenshot for details.
Proxyman-2

<!-- gh-comment-id:1931923923 --> @hcarstensen commented on GitHub (Feb 7, 2024): Update: Just had another request load being triggerd by some Google services. See Screenshot for details. ![Proxyman-2](https://github.com/ProxymanApp/Proxyman/assets/24648317/200f041d-fbb7-4d6a-a3bc-bf7db55feeb4)
Author
Owner

@NghiaTranUIT commented on GitHub (Feb 7, 2024):

It's really odd. Can you do Factory Reset in the Help menu -> Advance ?

I guess Proxyman is listening on port 9090, right?

<!-- gh-comment-id:1931945725 --> @NghiaTranUIT commented on GitHub (Feb 7, 2024): It's really odd. Can you do Factory Reset in the Help menu -> Advance ? I guess Proxyman is listening on port 9090, right?
Author
Owner

@hcarstensen commented on GitHub (Feb 7, 2024):

Did a factory reset including debug settings.
Same issue. After a few moments, it is back to requesting.
And yes, the port is 9090.

Currently Proxyman is unusable for me and all of my coworkers. Which is unfortunate, since we really love the tool and need it in our daily work.

Proxyman-3

<!-- gh-comment-id:1931961200 --> @hcarstensen commented on GitHub (Feb 7, 2024): Did a factory reset including debug settings. Same issue. After a few moments, it is back to requesting. And yes, the port is 9090. Currently Proxyman is unusable for me and all of my coworkers. Which is unfortunate, since we really love the tool and need it in our daily work. ![Proxyman-3](https://github.com/ProxymanApp/Proxyman/assets/24648317/db0f5ab0-26bf-4fb5-a6d5-f6ff1aca283d)
Author
Owner

@NghiaTranUIT commented on GitHub (Feb 7, 2024):

Sorry to hear that. Can you try one more thing: Adding ocsp.pki.goog to the Bypass Proxy List to see if it skips the request?

I believe that the Anti Virus causes the issue.

<!-- gh-comment-id:1931968351 --> @NghiaTranUIT commented on GitHub (Feb 7, 2024): Sorry to hear that. Can you try one more thing: Adding `ocsp.pki.goog` to the Bypass Proxy List to see if it skips the request? I believe that the Anti Virus causes the issue.
Author
Owner

@hcarstensen commented on GitHub (Feb 7, 2024):

It was stable for a moment, now I have the same issue with a new URL:
http://i4.c.eset.com/
This time it is POST request wich remains permanently active.

<!-- gh-comment-id:1931986020 --> @hcarstensen commented on GitHub (Feb 7, 2024): It was stable for a moment, now I have the same issue with a new URL: `http://i4.c.eset.com/ ` This time it is POST request wich remains permanently active.
Author
Owner

@hcarstensen commented on GitHub (Feb 7, 2024):

Added the new URL to the bypass list and now I am back to
http://update.eset.com/eset_upd/era_agent/update.ver.signed
Which is strange because update.eset.com is in the list as well.

<!-- gh-comment-id:1931992028 --> @hcarstensen commented on GitHub (Feb 7, 2024): Added the new URL to the bypass list and now I am back to `http://update.eset.com/eset_upd/era_agent/update.ver.signed` Which is strange because `update.eset.com` is in the list as well.
Author
Owner

@mpreikschat commented on GitHub (Feb 8, 2024):

Same issue here. Hope to see a solution in near future.

<!-- gh-comment-id:1933673602 --> @mpreikschat commented on GitHub (Feb 8, 2024): Same issue here. Hope to see a solution in near future.
Author
Owner

@hcarstensen commented on GitHub (Feb 8, 2024):

Short Update: I uninstalled ESET temporarily and the problem did not occur anymore. So it really seems to be an ESET problem.

Any chance we get an update soon?

<!-- gh-comment-id:1933675039 --> @hcarstensen commented on GitHub (Feb 8, 2024): _Short Update_: I uninstalled ESET temporarily and the problem did not occur anymore. So it really seems to be an ESET problem. Any chance we get an update soon?
Author
Owner

@NghiaTranUIT commented on GitHub (Feb 20, 2024):

@hcarstensen Not sure how to fix it on our side. I guess it's from the ESET.

Let me try to download the app (https://www.eset.com/us/download/) and reproduce it

<!-- gh-comment-id:1953417750 --> @NghiaTranUIT commented on GitHub (Feb 20, 2024): @hcarstensen Not sure how to fix it on our side. I guess it's from the ESET. Let me try to download the app (https://www.eset.com/us/download/) and reproduce it
Author
Owner

@NghiaTranUIT commented on GitHub (Feb 20, 2024):

@hcarstensen which one do you use? https://www.eset.com/us/home/protection-plans/

Is it an Ultimate with VPN and Identity Protection?

<!-- gh-comment-id:1953418715 --> @NghiaTranUIT commented on GitHub (Feb 20, 2024): @hcarstensen which one do you use? https://www.eset.com/us/home/protection-plans/ Is it an Ultimate with VPN and Identity Protection?
Author
Owner

@NghiaTranUIT commented on GitHub (Feb 20, 2024):

@hcarstensen Tried with the Home Version, and it just works fine. I guess the problem cause by the VPN. If you can try to turn off the VPN from ESET, it might fix the issue.

Screenshot 2024-02-20 at 10 25 24

<!-- gh-comment-id:1953428624 --> @NghiaTranUIT commented on GitHub (Feb 20, 2024): @hcarstensen Tried with the Home Version, and it just works fine. I guess the problem cause by the VPN. If you can try to turn off the VPN from ESET, it might fix the issue. ![Screenshot 2024-02-20 at 10 25 24](https://github.com/ProxymanApp/Proxyman/assets/5878421/14ad59b7-0f20-4865-a05a-5bfe7fb0e97d)
Author
Owner

@hcarstensen commented on GitHub (Feb 20, 2024):

Unfortunately I cannot disable ESET at will because I do not have permission.
Running ESET is a company-wide security policy and would require our system admin to deactivate it.

But let me try and give you some more information.

  1. The ESET product is called "ESET Endpoint Antivirus, V 7.4.1500.0".
  2. It provides "Web Protection", "Anti-Phishing Protection" and "E-Mail Protection", all of which are enabled by default.
  3. The macOS Network settings show a "Transparent Proxy" called "ESET Web&Email" which cannot be deactivated.

What I CAN do is disable the protections mentioned under 2.
But even then, as soon as ESET tries to update its signature files, the request load occurs.
Furthermore, I noticed that sometimes even opening a URL in Safari will trigger the issue. Proxyman will request the URL over and over again.

Also, I updated to the new Proxyman Version 5. Same issue.

<!-- gh-comment-id:1953759497 --> @hcarstensen commented on GitHub (Feb 20, 2024): Unfortunately I cannot disable ESET at will because I do not have permission. Running ESET is a company-wide security policy and would require our system admin to deactivate it. But let me try and give you some more information. 1. The ESET product is called "ESET Endpoint Antivirus, V 7.4.1500.0". 2. It provides "Web Protection", "Anti-Phishing Protection" and "E-Mail Protection", all of which are enabled by default. 3. The macOS Network settings show a "Transparent Proxy" called "ESET Web&Email" which cannot be deactivated. What I CAN do is disable the protections mentioned under 2. But even then, as soon as ESET tries to update its signature files, the request load occurs. Furthermore, I noticed that sometimes even opening a URL in Safari will trigger the issue. Proxyman will request the URL over and over again. Also, I updated to the new Proxyman Version 5. Same issue.
Author
Owner

@NghiaTranUIT commented on GitHub (Feb 20, 2024):

Thanks. I'm able to reproduce your issue. It happens when I click on the "Check for Update" button from the ESET Endpoint AntiVirus app.

Let me try to fix it and send you a BETA build asap 👍

<!-- gh-comment-id:1953843780 --> @NghiaTranUIT commented on GitHub (Feb 20, 2024): Thanks. I'm able to reproduce your issue. It happens when I click on the "Check for Update" button from the ESET Endpoint AntiVirus app. Let me try to fix it and send you a BETA build asap 👍
Author
Owner

@NghiaTranUIT commented on GitHub (Feb 26, 2024):

@hcarstensen @mpreikschat let's try this Beta build: https://download.proxyman.io/beta/Proxyman_5.0.0_Fix_ESET_Endpoint_Antivirus_issues.dmg

Changelog

  • Fix the loop issue when using Proxyman with ESET Endpoint Antivirus

Screenshot 2024-02-26 at 10 31 51

<!-- gh-comment-id:1963259743 --> @NghiaTranUIT commented on GitHub (Feb 26, 2024): @hcarstensen @mpreikschat let's try this Beta build: https://download.proxyman.io/beta/Proxyman_5.0.0_Fix_ESET_Endpoint_Antivirus_issues.dmg ### Changelog - Fix the loop issue when using Proxyman with ESET Endpoint Antivirus ![Screenshot 2024-02-26 at 10 31 51](https://github.com/ProxymanApp/Proxyman/assets/5878421/20431889-b617-4af4-98de-bf3a69db5521)
Author
Owner

@hcarstensen commented on GitHub (Feb 27, 2024):

Thanks for the update.
I installed the Beta and so far it's looking good.
I will let you know in case the issue returns unexpectedly.

<!-- gh-comment-id:1966580112 --> @hcarstensen commented on GitHub (Feb 27, 2024): Thanks for the update. I installed the Beta and so far it's looking good. I will let you know in case the issue returns unexpectedly.
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#1921
No description provided.