Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SSL Handshake Fails: Certificate Expiry Date Mismatch (Installed: 2026/1/1, Detected: 2025/1/1) in Proxyman Root CA #461

Open
Zhen-Bo opened this issue Jan 1, 2025 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@Zhen-Bo
Copy link

Zhen-Bo commented Jan 1, 2025

Description

SSL handshake fails when installing the root CA certificate on both Windows and rooted Android devices.

Steps to Reproduce

  1. Install Proxyman 2.18 or 2.19 on Windows
  2. Open Proxyman and go to General Settings
  3. Click "Generate New..." to install root CA in Windows
  4. Use a rooted mobile device and set up proxy to Proxyman
  5. Open mobile browser and visit cert.proxyman.io
  6. Save the CA file to device storage
  7. Go to mobile settings and install Proxyman root CA
  8. Execute the following commands:
su
mount -o rw,remount /
cp /data/misc/user/0/cacerts-added/*  /system/etc/security/cacerts/
mount -o ro,remount /
  1. Open Trusted Credentials to verify Proxyman root CA is installed (and confirm expiration date is 2026/1/1)
    PixPin_2025-01-01_17-39-21
    PixPin_2025-01-01_17-39-59
  2. Reboot device
  3. Open browser and visit google.com

Current Behavior

Browser displays "Your connection is not private" (certificate expiration date shows 2025/1/1)
PixPin_2025-01-01_17-43-07
Proxyman displays "SSL Handshake Failed"

Expected Behavior

Browser should display the web page normally
Proxyman should display the response

Environment

  • App version: 2.18 & 2.19
  • Windows/Linux version: Windows11 23H2
  • LDplayer 9.1.34.0(64) with Kitsune mask root (26.4-kitsune-2 (26400) and zygisk enable)
@Zhen-Bo Zhen-Bo added the bug Something isn't working label Jan 1, 2025
@Zhen-Bo
Copy link
Author

Zhen-Bo commented Jan 3, 2025

After regenerating and installing Proxyman's root certificate on my mobile device on January 3rd, the issue has been resolved, with the new certificate's expiration date returning to normal. This problem appears to only manifest when generating and installing the root certificate specifically on January 1st of each year.

@kics223w1
Copy link

Sorry for the late response, and thank you for resolving the issue. I'll add this issue to the To-Do list and investigate it at a convenient time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

No branches or pull requests

2 participants