mirror of
https://github.com/ProxymanApp/Proxyman.git
synced 2026-04-27 00:55:57 +03:00
[GH-ISSUE #1246] Last few releases not as reliable as older builds? #1241
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#1241
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 @ilendemli on GitHub (May 24, 2022).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1246
Proxyman version?
3.5.0 vs. 3.2.0
macOS Version?
macOS Monterey 12.3.1 (21E258)
Steps to reproduce
I have to use a proxy when connected to my company VPN (Checkpoint VPN), and I chose to use ProxyMan for this.
Not sure since when I have this Issue (3.4.0 and 3.5.0 have this Issues for sure), but when I enable ProxyMan, I get a bunch of Internal Error with Status Code 999 initially. After some time it works as expected, by itself. I can't reproduce the Issue with 3.2.0.
@NghiaTranUIT commented on GitHub (May 24, 2022):
From what I understand, there is no major change in the Proxy Core from Proxyman 3.5.0 and Proxyman 3.2.0. It's hard to pinpoint precisely whether or not the latest build is less reliable than the old build because the Checkpoint VPN is involved.
Basically, Proxyman might not work well with these VPNs apps, and I'm not sure if it's possible to fix it in our app.
I suppose that you might try:
@ilendemli commented on GitHub (May 24, 2022):
As I said, It worked before suddenly developing these issues. I reverted back to 3.2.0 and then back to 3.5.0. Resetting the Certificates did not change anything. I will continue observing for the next few days and report back if there is anything worth mentioning.
@NghiaTranUIT commented on GitHub (May 25, 2022):
Thanks. I would keep an eye on this issue too 👍
@ilendemli commented on GitHub (Aug 12, 2022):
I am not quite sure why this happens, but it may not be related to ProxyMan. Closing it for now.