mirror of
https://github.com/ProxymanApp/Proxyman.git
synced 2026-04-28 09:35:55 +03:00
[GH-ISSUE #1743] Unable to capture SSL traffic when NOT connected to the VPN #1736
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#1736
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 @albertbori on GitHub (Aug 17, 2023).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1743
Description
This is a really odd case. All of the help articles and troubleshooting resources I can find focus on how to get Proxyman to work while your VPN is running. However, when I disconnect and/or quit my VPN client, Proxyman will no longer correctly proxy any SSL traffic... ever... (I get
CONNECT 999 Internal Errortraffic for the domains in question.)No amount of restarting Proxyman, restarting the MacBook, or reinstalling Proxyman seems to fix the issue.
The SSL proxying works fantastically well, when connected to the VPN. Unfortunately I have some scenarios that need to be tested outside of the VPN connection and I'm unable to test those scenarios.
Notes:
Steps to Reproduce
Current Behavior
In Proxyman, experience
CONNECT 999 Internal Erroron all SSL traffic. No workarounds.Expected Behavior
In Proxyman, see normal/healthy SSL traffic
Environment
@NghiaTranUIT commented on GitHub (Aug 18, 2023):
It's difficult for me to reproduce it because I don't have Cisco AnyConnection VPN.
Just wondering: After the 5th step (
5. Disconnect from the VPN and/or quit the Cisco AnyConnect app), can you open the System Setting -> Wifi -> Your Wifi -> Details -> Proxies Tab -> Check if the HTTP/HTTPS Proxy is enabled? 🤔And if it's enabled, what values (IP, Port) are?
I assume that when the VPN is closed, it changes the HTTP/HTTPS Proxy value, so your traffic from your Mac is always disconnected.
@albertbori commented on GitHub (Aug 18, 2023):
Thanks for the quick reply. Here is the screenshot of my proxies view for the active network connection (Ethernet through a thunderbolt docking station). After Step 5, I opened the following settings menu and took a screenshot:

In addition, I still see the SSL connection attempts, but they all have
CONNECT 999errors:@NghiaTranUIT commented on GitHub (Aug 19, 2023):
@albertbori can you follow this:
/Applications/Proxyman.app/Contents/MacOS/ProxymanSecond question: Do you install the Helper Tools in Setting -> Advance Tab -> Helper Tool? 🤔
@albertbori commented on GitHub (Aug 19, 2023):
I'm pretty sure I installed this (I used the automatic setup). How do I verify that the helper tool is installed?
@NghiaTranUIT commented on GitHub (Aug 25, 2023):
It's in the Setting -> Advance Tab -> Helper Tool
@albertbori commented on GitHub (Aug 28, 2023):
Ok, thank you. I verified that it was installed.
I attempted to reproduce this issue so that I could follow the "Debug Mode" instructions you gave me above, but, to my surprise, Proxyman started capturing SSL traffic while disconnected from the VPN... I tried to reproduce the issue several more times, but Proxyman worked correctly each time.
¯\_(ツ)_/¯This is extremely odd to me because I've been able to reproduce this issue 100% of the time for the past couple of months. I even did several extensive and deep troubleshooting sessions to attempt to correct the issue in the past.Since I don't know why this issue suddenly self-resolved, I hesitate to call this issue "fixed". However, I can no longer reproduce the issue at this time, so we can probably close this ticket.
@albertbori commented on GitHub (Sep 19, 2023):
This issue has resurfaced with the same persistence as before. 😞 I am unable to inspect traffic for any SSL requests while not connected to the VPN and am unable to get my work done.
I have included the debug log output, as requested above.
Note that some domains were redacted for privacy reasons. The domain that caused the 999 error is
www.PROBLEM_REDACTED_FROM_LOGS.com(towards the bottom)@albertbori commented on GitHub (Sep 20, 2023):
Update: I discovered some potentially helpful info: This issue is isolated to traffic coming from the iOS Simulator.
Just to be sure it wasn't the certificate, I did:
@NghiaTranUIT commented on GitHub (Sep 21, 2023):
Sorry for the inconvenience, it's all about the AnyAconnect VPN, which is incompatible with Proxyman and Charles Proxy.
Not using VPN + Proxyman at the same time will always fix the issue.
@albertbori commented on GitHub (Oct 2, 2023):
I have good news! I did not find the source of the issue, but I did find a workaround. I was able to "un-break" the SSL proxying feature by toggling my wifi on/off and disconnecting and reconnecting my ethernet cable.
Backstory: I am connected to ethernet via a USB-C hub. Since some services (namely AnyConnect) often don't respect Network Service Order, I disabled my wifi adapter while connected to ethernet. At some point, the SSL proxying feature stops working only for the iOS simulator with that configuration. Not even rebooting would fix it.
By reenabling my wifi, and disconnecting/reconnecting my ethernet, the SSL proxying began working while disconnected from the VPN again.
I'm not sure whose fault this is, but I don't think it's Proxyman's. If I had to guess, it'd be either AnyConnect or Apple's iOS Simulator software.
Either way, we can close this issue as there's no reasonable path nor expectation for getting a permanent resolution for such an edge case, and there's a clear and consistent workaround.
Thanks for your help and support while I was troubleshooting this issue! 🙏
@NghiaTranUIT commented on GitHub (Oct 3, 2023):
Thanks for sharing your note 👍
I will keep an eye on the AnyConnect VPN issue and see if we can find any better solutions.