starred/Proxyman

Fork 0

mirror of https://github.com/ProxymanApp/Proxyman.git synced 2026-04-25 16:15:55 +03:00

[GH-ISSUE #1923] my http requests status is Internet Error #1914

New issue

Open

opened 2026-03-03 19:55:24 +03:00 by kerem · 6 comments

kerem commented

2026-03-03 19:55:24 +03:00

Owner

Originally created by @goundosunshine on GitHub (Jan 30, 2024).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1923

Description

My http request status is Internet Error when I enable the domain. I already reinstalled the certificate, erase all the data to restrart again but it still doesn't work

Steps to Reproduce

I have reinstalled my certificate, both to my Windows and Android Device.

Current Behavior

When I try to read the HTTP Request of my phone, they all have the status Internal Error

Expected Behavior

Monitor/Intercept all requests

Environment

App version: e.g Proxyman Latest
Windows version: e.g Windows 11

Originally created by @goundosunshine on GitHub (Jan 30, 2024). Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1923 ## Description  My http request status is Internet Error when I enable the domain. I already reinstalled the certificate, erase all the data to restrart again but it still doesn't work ## Steps to Reproduce  I have reinstalled my certificate, both to my Windows and Android Device. ## Current Behavior  When I try to read the HTTP Request of my phone, they all have the status Internal Error ![image](https://github.com/ProxymanApp/Proxyman/assets/119083693/e11facf0-9327-40c5-9fd9-ac9aabca3ac5) ## Expected Behavior  Monitor/Intercept all requests ## Environment - App version: e.g Proxyman Latest - Windows version: e.g Windows 11

kerem added the

bug

label

2026-03-03 19:55:24 +03:00

kerem commented

2026-03-03 19:55:25 +03:00

Author

Owner

@NghiaTranUIT commented on GitHub (Jan 30, 2024):

@goundosunshine it's not a bug. It's the security for Android devices.

You have to follow this Android Setup: https://docs.proxyman.io/debug-devices/android-device, especially step 5 you modify two files:

Add res/xml/network_security_config.xml
Add to AndroidManifest.xml

If not, you will get SSL Error as intended.

@NghiaTranUIT commented on GitHub (Jan 30, 2024): @goundosunshine it's not a bug. It's the security for Android devices. You have to follow this Android Setup: https://docs.proxyman.io/debug-devices/android-device, especially step 5 you modify two files: - Add res/xml/network_security_config.xml - Add to AndroidManifest.xml If not, you will get SSL Error as intended.

kerem commented

2026-03-03 19:55:25 +03:00

Author

Owner

@VictorIreri commented on GitHub (Jan 8, 2025):

I see this error but only when I connect a device to Proxyman for the first time after finishing all the setup steps. Then without me changing any configuration, it randomly starts working and it never happens again.
¯\_(ツ)_/¯

@VictorIreri commented on GitHub (Jan 8, 2025): I see this error but only when I connect a device to Proxyman for the first time after finishing all the setup steps. Then without me changing any configuration, it randomly starts working and it never happens again. ¯\\\_(ツ)_/¯

kerem commented

2026-03-03 19:55:25 +03:00

Author

Owner

@NghiaTranUIT commented on GitHub (Jan 8, 2025):

maybe it is a glitch from your Android device

@NghiaTranUIT commented on GitHub (Jan 8, 2025): maybe it is a glitch from your Android device

kerem commented

2026-03-03 19:55:25 +03:00

Author

Owner

@VictorIreri commented on GitHub (Jan 8, 2025):

Could be. It's happened on multiple Android devices though 😬
Next time this happens I can try checking the Android logcat and also Proxyman's error logs via Debug Mode.

@VictorIreri commented on GitHub (Jan 8, 2025): Could be. It's happened on multiple Android devices though 😬 Next time this happens I can try checking the Android logcat and also Proxyman's error logs via Debug Mode.

kerem commented

2026-03-03 19:55:26 +03:00

Author

Owner

@VictorIreri commented on GitHub (Jan 16, 2025):

I encountered the Internal Error again but unlike previous instances when it was on initial setup, this time it was on a device that had previously been set up but the device hadn't been used in a week. 🤔
Pixel 6a Android 15 + MacBook M1 Pro
I was getting the internal error on random APIs then I tried https://www.google.co.uk in Chrome and was getting the same but then a few minutes later after I closed and restarted Chrome (no other changes) it started working across all APIs.

Couldn't see anything in the Android logcat but Proxyman logged the following:

❌[ERROR] handshakeFailed(NIOSSL.BoringSSLError.sslError([Error: 268436502 error:10000416:SSL routines:OPENSSL_internal:SSLV3_ALERT_CERTIFICATE_UNKNOWN at /Users/nghiatran/Library/Developer/Xcode/DerivedData/NSProxy-chrjhjrygpkcrggquryyaaqcgvhz/SourcePackages/checkouts/swift-nio-ssl/Sources/CNIOBoringSSL/ssl/tls_record.cc:592]))

Also I don't encounter this when using Charles Proxy. 🤔

@VictorIreri commented on GitHub (Jan 16, 2025): I encountered the Internal Error again but unlike previous instances when it was on initial setup, this time it was on a device that had previously been set up but the device hadn't been used in a week. 🤔 Pixel 6a Android 15 + MacBook M1 Pro I was getting the internal error on random APIs then I tried `https://www.google.co.uk` in Chrome and was getting the same but then a few minutes later after I closed and restarted Chrome (no other changes) it started working across all APIs. ![Image](https://github.com/user-attachments/assets/234be541-633e-473f-80bb-a2004698269e) Couldn't see anything in the Android logcat but Proxyman logged the following: > ❌[ERROR] handshakeFailed(NIOSSL.BoringSSLError.sslError([Error: 268436502 error:10000416:SSL routines:OPENSSL_internal:SSLV3_ALERT_CERTIFICATE_UNKNOWN at /Users/nghiatran/Library/Developer/Xcode/DerivedData/NSProxy-chrjhjrygpkcrggquryyaaqcgvhz/SourcePackages/checkouts/swift-nio-ssl/Sources/CNIOBoringSSL/ssl/tls_record.cc:592])) Also I don't encounter this when using Charles Proxy. 🤔

kerem commented

2026-03-03 19:55:26 +03:00

Author

Owner

@VictorIreri commented on GitHub (Apr 8, 2025):

I'm still experiencing this on the latest version. There doesn't seem to be any reason why certain domains don't work and then when I trigger them a few seconds later they work just fine with no changes. Charles Proxy works just fine when I switch to it using the exact same setup. (I keep Charles Proxy closed when using Proxyman and vice versa). I've also seen this behaviour on my iOS device. I've also connected to different networks and seen the same behaviour.

Proxyman Version 5.17.0 (51700) | macOS: Version 14.7.5 (Build 23H527)

I'll try the Windows app to see if I can reproduce.

EDIT: I can't reproduce this any more on newer versions. Not sure what changed.
¯\_(ツ)_/¯

@VictorIreri commented on GitHub (Apr 8, 2025): I'm still experiencing this on the latest version. There doesn't seem to be any reason why certain domains don't work and then when I trigger them a few seconds later they work just fine with no changes. Charles Proxy works just fine when I switch to it using the exact same setup. (I keep Charles Proxy closed when using Proxyman and vice versa). I've also seen this behaviour on my iOS device. I've also connected to different networks and seen the same behaviour. Proxyman Version 5.17.0 (51700) | macOS: Version 14.7.5 (Build 23H527) I'll try the Windows app to see if I can reproduce. EDIT: I can't reproduce this any more on newer versions. Not sure what changed. ¯\\\_(ツ)_/¯