HTTPS request internal error for the first one

Description

• When using VPN (Quantumult X) together with Proxyman SSL Proxying, the first HTTPS request after startup always fails with an internal error (code 999).
• Sending the exact same request again (using Proxyman’s Repeat feature) succeeds with HTTP 200, which - confirms the request itself is valid and unchanged.
• This behavior reproduces every time after restarting Proxyman.

Steps to Reproduce

1. Enable VPN (Quantumult X) (without https mimt/ rewrite and so on, proxy for xxxx.com is DIRECT)
2. Launch Proxyman on macOS
3. Enable SSL Proxying with wildcard rule: *.xxxx.com （Proxyman）
4. Launch the iOS app on iPhone
5. Trigger an HTTPS request → This first request fails
6. Select the failed request in Proxyman and click Repeat → Repeat succeeds
7. Quit Proxyman
8. Relaunch Proxyman and repeat steps 4–6

Current Behavior

1. First HTTPS request after each Proxyman launch
   • Status: Internal Error
   • Code: 999
2. repeat the request
   • Status: Completed
   • Code: 200
3. After the first failure, all subsequent requests work normally

Expected Behavior

• The first HTTPS request after startup should succeed
• Behavior should be consistent across the requests

Environment

1. vpn quantumult X 1.5.4
2. macOS: Tahoe 26.0.1, Proxyman root certificate installed and trusted
3. Proxyman: Version 6.3.0 (60300)
4. iPhone 12： iOS 18.6.2, Proxyman trusted profile installed
5. SSL Proxying rule: *.xxxx.com

Reproduce the failure with Quantumult X, Proxyman 6.3.0, macOS Tahoe, and an iPhone using the listed wildcard SSL Proxying setup. Compare the first HTTPS request after launch with Proxyman’s Repeat request; done means the initial request succeeds with the expected HTTP 200 instead of internal error 999.