[GH-ISSUE #1743] Unable to capture SSL traffic when NOT connected to the VPN #1736

Closed
opened 2026-03-03 19:53:54 +03:00 by kerem · 11 comments
Owner

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 Error traffic 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:

  • Charles Proxy appears to proxy SSL traffic fine while disconnected from the VPN.
  • Physical devices connected to Proxyman over the network proxy SSL traffic fine wile disconnected from the VPN.
  • I have attempted to add the VPN domains to the Proxy Bypass list, to no avail.

Steps to Reproduce

  1. Launch Proxyman on an M1 MacBook Pro
  2. Launch and connect to VPN via Cisco AnyConnect
  3. Launch and test an iOS app via the iOS Simulator
  4. See that SSL traffic is successfully proxied in Proxyman
  5. Disconnect from the VPN and/or quit the Cisco AnyConnect app
  6. Launch and test an iOS app via the iOS Simulator

Current Behavior

In Proxyman, experience CONNECT 999 Internal Error on all SSL traffic. No workarounds.

Expected Behavior

In Proxyman, see normal/healthy SSL traffic

Environment

  • App version: 4.9.1 49001
  • macOS version: macOS Ventura 13.5 22G74
  • VPN: Cisco AnyConnect (4.10.03104)
  • Device Hardware: M1 MacBook Pro 14" 2021 32GB Ram
Originally created by @albertbori on GitHub (Aug 17, 2023). Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1743 ## Description <!--- Description for the bug? --> 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 Error` traffic 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: - Charles Proxy appears to proxy SSL traffic fine while disconnected from the VPN. - Physical devices connected to Proxyman over the network proxy SSL traffic fine wile disconnected from the VPN. - I have attempted to add the VPN domains to the Proxy Bypass list, to no avail. ## Steps to Reproduce <!-- Add relevant code and/or a live example --> 1. Launch Proxyman on an M1 MacBook Pro 2. Launch and connect to VPN via Cisco AnyConnect 3. Launch and test an iOS app via the iOS Simulator 4. See that SSL traffic is successfully proxied in Proxyman 5. Disconnect from the VPN and/or quit the Cisco AnyConnect app 6. Launch and test an iOS app via the iOS Simulator ## Current Behavior <!--- What went wrong? --> In Proxyman, experience `CONNECT 999 Internal Error` on all SSL traffic. No workarounds. ## Expected Behavior <!--- What should have happened? --> In Proxyman, see normal/healthy SSL traffic ## Environment - App version: 4.9.1 49001 - macOS version: macOS Ventura 13.5 22G74 - VPN: Cisco AnyConnect (4.10.03104) - Device Hardware: M1 MacBook Pro 14" 2021 32GB Ram
kerem 2026-03-03 19:53:54 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@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.

CleanShot 2023-08-18 at 09 31 27@2x

<!-- gh-comment-id:1683245636 --> @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. ![CleanShot 2023-08-18 at 09 31 27@2x](https://github.com/ProxymanApp/Proxyman/assets/5878421/b3d15fff-a44a-4623-ae3a-30e64fa98135)
Author
Owner

@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:
image

In addition, I still see the SSL connection attempts, but they all have CONNECT 999 errors:

image

<!-- gh-comment-id:1683271733 --> @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: ![image](https://github.com/ProxymanApp/Proxyman/assets/1742709/4734bd4c-c986-4ef3-b2a9-72574a112753) In addition, I still see the SSL connection attempts, but they all have `CONNECT 999` errors: ![image](https://github.com/ProxymanApp/Proxyman/assets/1742709/dc184177-e871-4834-a6cf-1a3c8e6cdb28)
Author
Owner

@NghiaTranUIT commented on GitHub (Aug 19, 2023):

@albertbori can you follow this:

  1. When you get this 999 error -> Help menu -> Advacend -> Enable Debug Mode.
  2. Close Proxyman app and start the app again by using the command line: /Applications/Proxyman.app/Contents/MacOS/Proxyman
  3. Try to reproduce the issue again, and share with me the error log.

Second question: Do you install the Helper Tools in Setting -> Advance Tab -> Helper Tool? 🤔

<!-- gh-comment-id:1684677987 --> @NghiaTranUIT commented on GitHub (Aug 19, 2023): @albertbori can you follow this: 1. When you get this 999 error -> Help menu -> Advacend -> Enable Debug Mode. 2. Close Proxyman app and start the app again by using the command line: `/Applications/Proxyman.app/Contents/MacOS/Proxyman` 3. Try to reproduce the issue again, and share with me the error log. Second question: Do you install the Helper Tools in Setting -> Advance Tab -> Helper Tool? 🤔
Author
Owner

@albertbori commented on GitHub (Aug 19, 2023):

Second question: Do you install the Helper Tools in Setting -> Advance Tab -> Helper Tool? 🤔

I'm pretty sure I installed this (I used the automatic setup). How do I verify that the helper tool is installed?

<!-- gh-comment-id:1684944080 --> @albertbori commented on GitHub (Aug 19, 2023): > Second question: Do you install the Helper Tools in Setting -> Advance Tab -> Helper Tool? 🤔 I'm pretty sure I installed this (I used the automatic setup). How do I verify that the helper tool is installed?
Author
Owner

@NghiaTranUIT commented on GitHub (Aug 25, 2023):

It's in the Setting -> Advance Tab -> Helper Tool

CleanShot 2023-08-25 at 15 50 02@2x

<!-- gh-comment-id:1693009827 --> @NghiaTranUIT commented on GitHub (Aug 25, 2023): It's in the Setting -> Advance Tab -> Helper Tool ![CleanShot 2023-08-25 at 15 50 02@2x](https://github.com/ProxymanApp/Proxyman/assets/5878421/28e8726b-1b96-4971-b446-b0e5a9152c5a)
Author
Owner

@albertbori commented on GitHub (Aug 28, 2023):

Second question: Do you install the Helper Tools in Setting -> Advance Tab -> Helper Tool? 🤔

I'm pretty sure I installed this (I used the automatic setup). How do I verify that the helper tool is installed?

It's in the Setting -> Advance Tab -> Helper Tool

Ok, thank you. I verified that it was installed.

When you get this 999 error -> Help menu -> Advacend -> Enable Debug Mode.

  1. Close Proxyman app and start the app again by using the command line: /Applications/Proxyman.app/Contents/MacOS/Proxyman
  2. Try to reproduce the issue again, and share with me the error log.

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.

<!-- gh-comment-id:1695700727 --> @albertbori commented on GitHub (Aug 28, 2023): >>> Second question: Do you install the Helper Tools in Setting -> Advance Tab -> Helper Tool? 🤔 >> I'm pretty sure I installed this (I used the automatic setup). How do I verify that the helper tool is installed? > It's in the Setting -> Advance Tab -> Helper Tool Ok, thank you. I verified that it was installed. > When you get this 999 error -> Help menu -> Advacend -> Enable Debug Mode. > 1. Close Proxyman app and start the app again by using the command line: `/Applications/Proxyman.app/Contents/MacOS/Proxyman` > 2. Try to reproduce the issue again, and share with me the error log. 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.
Author
Owner

@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)

2023-09-19 10:22:50.588 Proxyman[7461:81783] [HelperTool] New version 1.4.0 and Current Version 1.4.0
[MonacoEditor] Start at port 10258
2023-09-19 10:22:50.979 Proxyman[7461:81819] [HelperTool] New version 1.4.0 and Current Version 1.4.0
[HelperToolSuggestion] Skip because the user ask for it!
2023-09-19 10:22:51.040 Proxyman[7461:81758] version = 1.4.0
✅ [NetworkSystem] HTTP Override by HelperTool (New APIs)
[DEBUG] Connecting to www.googleapis.com:443
----- ✅ Try to searching for www.googleapis.com:443
2023-09-19 10:22:51.109 Proxyman[7461:81758] version = 1.4.0
[DEBUG] Connecting to proxyman.io:443
----- ✅ Try to searching for proxyman.io:443
[DEBUG] Connecting to fcmconnection.googleapis.com:443
----- ✅ Try to searching for fcmconnection.googleapis.com:443
[DEBUG] Connecting to fcmconnection.googleapis.com:443
----- ✅ Found cache for fcmconnection.googleapis.com:443
[DEBUG] Connecting to in.appcenter.ms:443
----- ✅ Try to searching for in.appcenter.ms:443
[DEBUG] Connecting to github.REDACTED_FROM_LOGS.com:443
----- ✅ Try to searching for github.REDACTED_FROM_LOGS.com:443
[DEBUG] Connecting to appstoreconnect.apple.com:443
----- ✅ Try to searching for appstoreconnect.apple.com:443
[DEBUG] Connecting to REDACTED_FROM_LOGS.service.REDACTED_FROM_LOGS.com:443
----- ✅ Try to searching for REDACTED_FROM_LOGS.service.REDACTED_FROM_LOGS.com:443
❌[ERROR] Connect failed: at host = Optional("in.appcenter.ms"), port = Optional(443): connectTimeout(NIOCore.TimeAmount(nanoseconds: 10000000000))
[DEBUG] Connecting to in.appcenter.ms:443
----- ✅ Found cache for in.appcenter.ms:443
2023-09-19 10:23:06.761 Proxyman[7461:82274] [AppCenter] ERROR: -[MSACHttpClient requestCompletedWithHttpCall:data:response:error:]/151 HTTP request error with code: -1000, domain: NSURLErrorDomain, description: bad URL
2023-09-19 10:23:06.761 Proxyman[7461:82274] [AppCenter] ERROR: -[MSACChannelUnitDefault sendLogContainer:]_block_invoke/230 Log(s) sent with failure, batch Id:347D63EA-9194-4861-B67B-D8287EC2F8CD, status code:0
[DEBUG] Connecting to init.sandbox.push.apple.com:443
----- ✅ Try to searching for init.sandbox.push.apple.com:443
[DEBUG] Connecting to chat.google.com:443
----- ✅ Try to searching for chat.google.com:443
[DEBUG] Connecting to drivefrontend-pa.googleapis.com:443
----- ✅ Try to searching for drivefrontend-pa.googleapis.com:443
[DEBUG] Connecting to configuration.ls.apple.com:443
[DEBUG] Connecting to gspe1-ssl.ls.apple.com:443
----- ✅ Try to searching for gspe1-ssl.ls.apple.com:443
----- ✅ Try to searching for configuration.ls.apple.com:443
[DEBUG] Connecting to bag.itunes.apple.com:443
----- ✅ Try to searching for bag.itunes.apple.com:443
[DEBUG] Connecting to mesu.apple.com:443
----- ✅ Try to searching for mesu.apple.com:443
[DEBUG] Connecting to gdmf.apple.com:443
----- ✅ Try to searching for gdmf.apple.com:443
[DEBUG] Connecting to ssl.gstatic.com:443
----- ✅ Try to searching for ssl.gstatic.com:443
[DEBUG] Connecting to mesu.apple.com:443
----- ✅ Found cache for mesu.apple.com:443
[DEBUG] Connecting to gdmf.apple.com:443
----- ✅ Found cache for gdmf.apple.com:443
[DEBUG] Connecting to xp.apple.com:443
----- ✅ Try to searching for xp.apple.com:443
[DEBUG] Connecting to github.REDACTED_FROM_LOGS.com:443
----- ✅ Found cache for github.REDACTED_FROM_LOGS.com:443
[DEBUG] Connecting to c.riskified.com:443
----- ✅ Try to searching for c.riskified.com:443
----- ✅ Found cache for c.riskified.com:443
[DEBUG] Connecting to c.riskified.com:443
----- ✅ Found cache for c.riskified.com:443
❌[ERROR] Connect failed: at host = Optional("in.appcenter.ms"), port = Optional(443): connectTimeout(NIOCore.TimeAmount(nanoseconds: 10000000000))
2023-09-19 10:23:16.765 Proxyman[7461:82282] [AppCenter] ERROR: -[MSACHttpClient requestCompletedWithHttpCall:data:response:error:]/151 HTTP request error with code: -1000, domain: NSURLErrorDomain, description: bad URL
2023-09-19 10:23:16.765 Proxyman[7461:82282] [AppCenter] ERROR: -[MSACChannelUnitDefault sendLogContainer:]_block_invoke/230 Log(s) sent with failure, batch Id:975F643B-0EAD-458C-9E0D-C6AEAEECF299, status code:0
[DEBUG] Connecting to www.PROBLEM_REDACTED_FROM_LOGS.com:443
----- ✅ Try to searching for www.PROBLEM_REDACTED_FROM_LOGS.com:443
[DEBUG] Connecting to safebrowsing.googleapis.com:443
----- ✅ Try to searching for safebrowsing.googleapis.com:443
[DEBUG] Connecting to ssl.gstatic.com:443
----- ✅ Found cache for ssl.gstatic.com:443
[DEBUG] Connecting to www.PROBLEM_REDACTED_FROM_LOGS.com:443
❌[ERROR] handshakeFailed(NIOSSL.BoringSSLError.sslError([Error:  EOF during handshake]))
❌[ERROR] handshakeFailed(NIOSSL.BoringSSLError.sslError([Error:  EOF during handshake]))
<!-- gh-comment-id:1725765622 --> @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) ``` 2023-09-19 10:22:50.588 Proxyman[7461:81783] [HelperTool] New version 1.4.0 and Current Version 1.4.0 [MonacoEditor] Start at port 10258 2023-09-19 10:22:50.979 Proxyman[7461:81819] [HelperTool] New version 1.4.0 and Current Version 1.4.0 [HelperToolSuggestion] Skip because the user ask for it! 2023-09-19 10:22:51.040 Proxyman[7461:81758] version = 1.4.0 ✅ [NetworkSystem] HTTP Override by HelperTool (New APIs) [DEBUG] Connecting to www.googleapis.com:443 ----- ✅ Try to searching for www.googleapis.com:443 2023-09-19 10:22:51.109 Proxyman[7461:81758] version = 1.4.0 [DEBUG] Connecting to proxyman.io:443 ----- ✅ Try to searching for proxyman.io:443 [DEBUG] Connecting to fcmconnection.googleapis.com:443 ----- ✅ Try to searching for fcmconnection.googleapis.com:443 [DEBUG] Connecting to fcmconnection.googleapis.com:443 ----- ✅ Found cache for fcmconnection.googleapis.com:443 [DEBUG] Connecting to in.appcenter.ms:443 ----- ✅ Try to searching for in.appcenter.ms:443 [DEBUG] Connecting to github.REDACTED_FROM_LOGS.com:443 ----- ✅ Try to searching for github.REDACTED_FROM_LOGS.com:443 [DEBUG] Connecting to appstoreconnect.apple.com:443 ----- ✅ Try to searching for appstoreconnect.apple.com:443 [DEBUG] Connecting to REDACTED_FROM_LOGS.service.REDACTED_FROM_LOGS.com:443 ----- ✅ Try to searching for REDACTED_FROM_LOGS.service.REDACTED_FROM_LOGS.com:443 ❌[ERROR] Connect failed: at host = Optional("in.appcenter.ms"), port = Optional(443): connectTimeout(NIOCore.TimeAmount(nanoseconds: 10000000000)) [DEBUG] Connecting to in.appcenter.ms:443 ----- ✅ Found cache for in.appcenter.ms:443 2023-09-19 10:23:06.761 Proxyman[7461:82274] [AppCenter] ERROR: -[MSACHttpClient requestCompletedWithHttpCall:data:response:error:]/151 HTTP request error with code: -1000, domain: NSURLErrorDomain, description: bad URL 2023-09-19 10:23:06.761 Proxyman[7461:82274] [AppCenter] ERROR: -[MSACChannelUnitDefault sendLogContainer:]_block_invoke/230 Log(s) sent with failure, batch Id:347D63EA-9194-4861-B67B-D8287EC2F8CD, status code:0 [DEBUG] Connecting to init.sandbox.push.apple.com:443 ----- ✅ Try to searching for init.sandbox.push.apple.com:443 [DEBUG] Connecting to chat.google.com:443 ----- ✅ Try to searching for chat.google.com:443 [DEBUG] Connecting to drivefrontend-pa.googleapis.com:443 ----- ✅ Try to searching for drivefrontend-pa.googleapis.com:443 [DEBUG] Connecting to configuration.ls.apple.com:443 [DEBUG] Connecting to gspe1-ssl.ls.apple.com:443 ----- ✅ Try to searching for gspe1-ssl.ls.apple.com:443 ----- ✅ Try to searching for configuration.ls.apple.com:443 [DEBUG] Connecting to bag.itunes.apple.com:443 ----- ✅ Try to searching for bag.itunes.apple.com:443 [DEBUG] Connecting to mesu.apple.com:443 ----- ✅ Try to searching for mesu.apple.com:443 [DEBUG] Connecting to gdmf.apple.com:443 ----- ✅ Try to searching for gdmf.apple.com:443 [DEBUG] Connecting to ssl.gstatic.com:443 ----- ✅ Try to searching for ssl.gstatic.com:443 [DEBUG] Connecting to mesu.apple.com:443 ----- ✅ Found cache for mesu.apple.com:443 [DEBUG] Connecting to gdmf.apple.com:443 ----- ✅ Found cache for gdmf.apple.com:443 [DEBUG] Connecting to xp.apple.com:443 ----- ✅ Try to searching for xp.apple.com:443 [DEBUG] Connecting to github.REDACTED_FROM_LOGS.com:443 ----- ✅ Found cache for github.REDACTED_FROM_LOGS.com:443 [DEBUG] Connecting to c.riskified.com:443 ----- ✅ Try to searching for c.riskified.com:443 ----- ✅ Found cache for c.riskified.com:443 [DEBUG] Connecting to c.riskified.com:443 ----- ✅ Found cache for c.riskified.com:443 ❌[ERROR] Connect failed: at host = Optional("in.appcenter.ms"), port = Optional(443): connectTimeout(NIOCore.TimeAmount(nanoseconds: 10000000000)) 2023-09-19 10:23:16.765 Proxyman[7461:82282] [AppCenter] ERROR: -[MSACHttpClient requestCompletedWithHttpCall:data:response:error:]/151 HTTP request error with code: -1000, domain: NSURLErrorDomain, description: bad URL 2023-09-19 10:23:16.765 Proxyman[7461:82282] [AppCenter] ERROR: -[MSACChannelUnitDefault sendLogContainer:]_block_invoke/230 Log(s) sent with failure, batch Id:975F643B-0EAD-458C-9E0D-C6AEAEECF299, status code:0 [DEBUG] Connecting to www.PROBLEM_REDACTED_FROM_LOGS.com:443 ----- ✅ Try to searching for www.PROBLEM_REDACTED_FROM_LOGS.com:443 [DEBUG] Connecting to safebrowsing.googleapis.com:443 ----- ✅ Try to searching for safebrowsing.googleapis.com:443 [DEBUG] Connecting to ssl.gstatic.com:443 ----- ✅ Found cache for ssl.gstatic.com:443 [DEBUG] Connecting to www.PROBLEM_REDACTED_FROM_LOGS.com:443 ❌[ERROR] handshakeFailed(NIOSSL.BoringSSLError.sslError([Error: EOF during handshake])) ❌[ERROR] handshakeFailed(NIOSSL.BoringSSLError.sslError([Error: EOF during handshake])) ```
Author
Owner

@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:

  1. Certificate > Install Certificate on iOS > Simulators...
  2. Install Root Proxyman Certificate to this Mac: Installed
  3. Install and Trust the certificate to running Simulators: Installed
  4. Reboot iOS Simulators: Rebooted!
    image
<!-- gh-comment-id:1728142576 --> @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: 1. Certificate > Install Certificate on iOS > Simulators... 2. Install Root Proxyman Certificate to this Mac: ✅ Installed 3. Install and Trust the certificate to running Simulators: ✅ Installed 4. Reboot iOS Simulators: ✅ Rebooted! ![image](https://github.com/ProxymanApp/Proxyman/assets/1742709/4d5b0e9e-5cd6-451a-8e58-7a78cc7fe314)
Author
Owner

@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.

<!-- gh-comment-id:1728668772 --> @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.
Author
Owner

@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! 🙏

<!-- gh-comment-id:1743666533 --> @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! 🙏
Author
Owner

@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.

<!-- gh-comment-id:1744016250 --> @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.
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#1736
No description provided.