mirror of
https://github.com/ProxymanApp/Proxyman.git
synced 2026-04-26 00:25:56 +03:00
[GH-ISSUE #1524] Internal error after enabling SSL proxying #1518
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#1518
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 @adambasek on GitHub (Feb 7, 2023).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1524
Description
I have installed Proxyman on both Mac and Iphone XR. Was able to link them and was able to see the traffic from various apps. But after enabling SSL Proxying I started to see Internal Error (without any details) on pages for which I had enabled the SSL. Same time I was not able to enter the enabled page on Iphone any more (e.g. google.com) as my Iphone displayed information that connection is not secure. Same happens for other sites. Certificates were properly installed & enabled on both Mac and Iphone (General > VPN Management, About > Certificate Trust Settings, Proxy was configures, VPN disabled)
Current Behavior
Internal error for pages where SSL proxying were enabled
Expected Behavior
Decrypted responses should be displayed
Environment
@NghiaTranUIT commented on GitHub (Feb 7, 2023):
Look like you're using Proxyman for iOS and macOS at the same time?
Please note that it should use separately.
If you decide to use the Proxyman for macOS app, please close and quit the Proxyman for iOS app (Turn off the Proxyman VPN too). Then following the iOS Guide at https://docs.proxyman.io/debug-devices/ios-device
@adambasek commented on GitHub (Feb 7, 2023):
Thank you. I followed your comment and it works!