[GH-ISSUE #763] 999 Errors when „enable HTTPS Response“ #759

Open
opened 2026-03-03 19:21:39 +03:00 by kerem · 9 comments
Owner

Originally created by @tibor on GitHub (Jan 25, 2021).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/763

Hi, I tested Proxyman the first time 2 weeks ago and everything went fine. Today I wanted to test a little bit more and I was able to get my iPhone connected to the Mac and see all requests. However, when I turned on „enable HTTPS Response“ for any domain, I would only see 999 Errors.

I deleted the certificate on both iPhone and Mac, but the problem stays the same. Do you have any idea how to fix this?

Thanks in advance!

Proxyman version? (Ex. Proxyman 1.4.3)

2.16.1

macOS Version? (Ex. mac 10.14)

10.14.6

Steps to reproduce

Expected behavior

Proxyman would be able to read HTTPS responses the same way as HTTP responses

Screenshots (optional)

Originally created by @tibor on GitHub (Jan 25, 2021). Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/763 Hi, I tested Proxyman the first time 2 weeks ago and everything went fine. Today I wanted to test a little bit more and I was able to get my iPhone connected to the Mac and see all requests. However, when I turned on „enable HTTPS Response“ for any domain, I would only see 999 Errors. I deleted the certificate on both iPhone and Mac, but the problem stays the same. Do you have any idea how to fix this? Thanks in advance! ### Proxyman version? (Ex. Proxyman 1.4.3) 2.16.1 ### macOS Version? (Ex. mac 10.14) 10.14.6 ### Steps to reproduce ### Expected behavior Proxyman would be able to read HTTPS responses the same way as HTTP responses ### Screenshots (optional)
Author
Owner

@NghiaTranUIT commented on GitHub (Jan 25, 2021):

Hi, can you try to reset Factory in Help -> Advanced -> Reset to see if it works?

<!-- gh-comment-id:766756253 --> @NghiaTranUIT commented on GitHub (Jan 25, 2021): Hi, can you try to reset Factory in Help -> Advanced -> Reset to see if it works?
Author
Owner

@tibor commented on GitHub (Jan 25, 2021):

Hi @NghiaTranUIT, thanks for the fast answer! Tried this but the result stays the same. I also renewed the SSL certificate on my iPhone again.

<!-- gh-comment-id:766798493 --> @tibor commented on GitHub (Jan 25, 2021): Hi @NghiaTranUIT, thanks for the fast answer! Tried this but the result stays the same. I also renewed the SSL certificate on my iPhone again.
Author
Owner

@NghiaTranUIT commented on GitHub (Jan 25, 2021):

Can you try to intercept google.com from Safari on iOS to verify if you config properly

<!-- gh-comment-id:766799735 --> @NghiaTranUIT commented on GitHub (Jan 25, 2021): Can you try to intercept google.com from Safari on iOS to verify if you config properly
Author
Owner

@tibor commented on GitHub (Jan 25, 2021):

You mean going to google.com on my iPhone and checking what happens?

<!-- gh-comment-id:766848546 --> @tibor commented on GitHub (Jan 25, 2021): You mean going to google.com on my iPhone and checking what happens?
Author
Owner

@NghiaTranUIT commented on GitHub (Jan 25, 2021):

Yes. It’s. Just open Safari and try intercept google.com. If you setup correctly, you can see the response.

Here is the troubleshooting https://docs.proxyman.io/troubleshooting/get-ssl-error-from-https-request-and-response

<!-- gh-comment-id:766850362 --> @NghiaTranUIT commented on GitHub (Jan 25, 2021): Yes. It’s. Just open Safari and try intercept google.com. If you setup correctly, you can see the response. Here is the troubleshooting https://docs.proxyman.io/troubleshooting/get-ssl-error-from-https-request-and-response
Author
Owner

@NghiaTranUIT commented on GitHub (Jan 26, 2021):

@tibor please follow the "2.1 Verify that you're able to see other HTTPS Response without error" section on the troubleshooting page, it will guide you on how to debug what the bug is 👍

<!-- gh-comment-id:767226922 --> @NghiaTranUIT commented on GitHub (Jan 26, 2021): @tibor please follow the "2.1 Verify that you're able to see other HTTPS Response without error" section on the troubleshooting page, it will guide you on how to debug what the bug is 👍
Author
Owner

@fannar commented on GitHub (Mar 8, 2021):

Having the same problem. 999 ERROR even for https://www.google.com in mobile Safari (iOS). Gone over everything twice on the Troubleshoot page and tried the Help->Advanced-Reset method. No luck.

<!-- gh-comment-id:793151491 --> @fannar commented on GitHub (Mar 8, 2021): Having the same problem. **999 ERROR** even for https://www.google.com in mobile Safari (iOS). Gone over everything twice on the Troubleshoot page and tried the Help->Advanced-Reset method. No luck.
Author
Owner

@NghiaTranUIT commented on GitHub (Mar 8, 2021):

Hey @fannar can you try google.com in your safari on MacBook. Does it work?

and what is your iOS version you’re using 🤔

<!-- gh-comment-id:793162485 --> @NghiaTranUIT commented on GitHub (Mar 8, 2021): Hey @fannar can you try google.com in your safari on MacBook. Does it work? and what is your iOS version you’re using 🤔
Author
Owner

@fannar commented on GitHub (Mar 9, 2021):

Hey @NghiaTranUIT. Found out what the problem was. It was me 🤓
General->About->Certificates Trust Settings was off.

<!-- gh-comment-id:793617868 --> @fannar commented on GitHub (Mar 9, 2021): Hey @NghiaTranUIT. Found out what the problem was. It was me 🤓 **General->About->Certificates Trust Settings** was **off**.
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#759
No description provided.