mirror of
https://github.com/ProxymanApp/Proxyman.git
synced 2026-04-27 09:05:54 +03:00
[GH-ISSUE #1303] Android: Devices not accepting/installing proxyman-generated certificates #1297
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#1297
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 @carstenhag on GitHub (Jul 22, 2022).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1303
Originally assigned to: @NghiaTranUIT on GitHub.
I recently switched from a 2019 intel MacBook to a new m1 MacBook. With the intel one is was on Proxyman 3.6.1 and everything worked fine. Now I am setting up the m1 one and on the mac everything works, but the devices don't seem to like the certificates anymore.
Tried to google for the issue, as I thought it's the device's fault, but couldn't find much info at all.
Proxyman version? (Ex. Proxyman 1.4.3)
3.7.0
macOS Version? (Ex. mac 10.14)
macOS 12.3
Steps to reproduce
Devices
Tried this both on a Samsung A70 (Android 11) and an OnePlus8 (Android 11).
Expected behavior
Certificate is installed
Screenshots (optional)
@NghiaTranUIT commented on GitHub (Jul 22, 2022):
Can you verify that:
It means: Settings app -> Security -> Encryption & Credentials -> Install a Certificate -> Selec "CA Certificate" -> Select Proxyman CA Certificate in your storage. ?
Reference: https://docs.proxyman.io/debug-devices/android-device#android-setup-guide
@carstenhag commented on GitHub (Jul 22, 2022):
Yes, exactly that.
@carstenhag commented on GitHub (Jul 22, 2022):
Getting the same error (but only in a toast) by running this ADB command:
adb shell am start -n com.android.certinstaller/.CertInstallerMain -a android.intent.action.VIEW -t application/x-x509-ca-cert -d file:///storage/self/primary/Download/proxyman-ca.pem.crt@NghiaTranUIT commented on GitHub (Jul 22, 2022):
Thanks. Since I don't have physical android device, I'm downloading Android 11 Emulator and test again
@carstenhag commented on GitHub (Jul 22, 2022):
Will also try it out on an emulator. This is the certificate that the device downloaded https://drive.google.com/file/d/1u1kCY9Kd2rLo74O0XTuBxv5z9Xg23n2_/view?usp=sharing
@NghiaTranUIT commented on GitHub (Jul 22, 2022):
The certificate looks ok, I don't see any "null" field. Going to investigate now
@NghiaTranUIT commented on GitHub (Jul 22, 2022):
@carstenhag if you use Android Emulator, can you use the Automatic Script in the Certificate menu -> Install on Android -> Emulator -> Override?
@NghiaTranUIT commented on GitHub (Jul 22, 2022):
@carstenhag I could not reproduce it. I'm able to manually install the certificate in Android 11 Emulator
@NghiaTranUIT commented on GitHub (Jul 22, 2022):
Maybe reset the certificate (Tool -> Reset all certificate) might work?
@carstenhag commented on GitHub (Jul 22, 2022):
Found the issue. I was trying to install it as "VPN or App certificate", but the correct option is "CA certificate". Sorry for the trouble :)
@carstenhag commented on GitHub (Jul 22, 2022):
Actually it would be great if you could add this to the troubleshooting page :)