starred/proxyman-windows-linux

Fork 0

mirror of https://github.com/ProxymanApp/proxyman-windows-linux.git synced 2026-04-27 00:45:55 +03:00

[GH-ISSUE #532] Proxyman Certificate Installation Fails on Windows #529

New issue

Closed

opened 2026-03-03 19:51:10 +03:00 by kerem · 9 comments

kerem commented

2026-03-03 19:51:10 +03:00

Owner

Originally created by @K-4RMA on GitHub (Aug 15, 2025).
Original GitHub issue: https://github.com/ProxymanApp/proxyman-windows-linux/issues/532

Originally assigned to: @kics223w1 on GitHub.

Description

C:\Users\MYNAME\AppData\Roaming\Proxyman\certificate\certs\ca.cer.

When attempting to open the file, Windows reports:
Invalid public key security object / This file is not valid for use as a security certificate.

Additionally, Proxyman initially shows:
Error: Too few bytes to read ASN.1 value. Please install your certificate again.

As a result, the root certificate cannot be installed, and HTTPS traffic cannot be proxied.

Steps to Reproduce

Install Proxyman Version 3.1.0 (31000) on Windows 11 Pro (Version 24H2, Build 26100.3476).
Generate the certificate in Proxyman.
Navigate to C:\Users\MYNAME\AppData\Roaming\Proxyman\certificate\certs\ca.cer.
Double-click the ca.cer file.
Observe the ASN.1 error in Proxyman and the invalid certificate error in Windows.

Current Behavior

Proxyman shows: Error: Too few bytes to read ASN.1 value. Please install your certificate again.
The ca.cer file cannot be opened in Windows.
Root certificate installation fails.
HTTPS traffic cannot be proxied.

Expected Behavior

Certificate should generate correctly without ASN.1 errors.
Double-clicking ca.cer should launch Windows certificate import wizard successfully.
Root certificate should be installed in the root store.
HTTPS traffic should be proxied correctly.

Environment

App version: Proxyman Version 3.1.0 (31000)
OS: Windows 11 Pro
Version: 24H2
OS Build: 26100.3476

Originally created by @K-4RMA on GitHub (Aug 15, 2025). Original GitHub issue: https://github.com/ProxymanApp/proxyman-windows-linux/issues/532 Originally assigned to: @kics223w1 on GitHub. # Description `C:\Users\MYNAME\AppData\Roaming\Proxyman\certificate\certs\ca.cer`. When attempting to open the file, Windows reports: `Invalid public key security object / This file is not valid for use as a security certificate.` Additionally, Proxyman initially shows: `Error: Too few bytes to read ASN.1 value. Please install your certificate again.` As a result, the root certificate cannot be installed, and HTTPS traffic cannot be proxied. --- # Steps to Reproduce 1. Install Proxyman Version 3.1.0 (31000) on Windows 11 Pro (Version 24H2, Build 26100.3476). 2. Generate the certificate in Proxyman. 3. Navigate to `C:\Users\MYNAME\AppData\Roaming\Proxyman\certificate\certs\ca.cer`. 4. Double-click the `ca.cer` file. 5. Observe the ASN.1 error in Proxyman and the invalid certificate error in Windows. --- # Current Behavior - Proxyman shows: `Error: Too few bytes to read ASN.1 value. Please install your certificate again.` - The `ca.cer` file cannot be opened in Windows. - Root certificate installation fails. - HTTPS traffic cannot be proxied. --- # Expected Behavior - Certificate should generate correctly without ASN.1 errors. - Double-clicking `ca.cer` should launch Windows certificate import wizard successfully. - Root certificate should be installed in the root store. - HTTPS traffic should be proxied correctly. --- # Environment - App version: Proxyman Version 3.1.0 (31000) - OS: Windows 11 Pro - Version: 24H2 - OS Build: 26100.3476 ---

kerem

2026-03-03 19:51:10 +03:00

closed this issue
added the
✅ Done

bug
labels

kerem commented

2026-03-03 19:51:11 +03:00

Author

Owner

@kics223w1 commented on GitHub (Aug 15, 2025):

Hi @DongjuTheDeveloper,

Please try deleting the certs folder and relaunching Proxyman. This will generate a new certificate.
After that, install the new certificate and test again.

We haven’t made any changes to certificate handling in Proxyman 3.1.0.

@kics223w1 commented on GitHub (Aug 15, 2025): Hi @DongjuTheDeveloper, Please try deleting the certs folder and relaunching Proxyman. This will generate a new certificate. After that, install the new certificate and test again. We haven’t made any changes to certificate handling in Proxyman 3.1.0.

kerem commented

2026-03-03 19:51:11 +03:00

Author

Owner

@K-4RMA commented on GitHub (Aug 15, 2025):

I kept trying this and even uninstalled and reinstalled the program, but the problem was not solved.

@K-4RMA commented on GitHub (Aug 15, 2025): I kept trying this and even uninstalled and reinstalled the program, but the problem was not solved.

kerem commented

2026-03-03 19:51:11 +03:00

Author

Owner

@kics223w1 commented on GitHub (Aug 15, 2025):

Does this also happen on version 3.0.0? 🤔
Does the automatic certificate installation feature work correctly? It installs the ca.pem file, not ca.cer.

@kics223w1 commented on GitHub (Aug 15, 2025): Does this also happen on version 3.0.0? 🤔 Does the automatic certificate installation feature work correctly? It installs the ca.pem file, not ca.cer.

kerem commented

2026-03-03 19:51:11 +03:00

Author

Owner

@K-4RMA commented on GitHub (Aug 15, 2025):

I did a fresh install of Proxyman Version 3.0.0 (30000) | Windows (Build 10.0.26100) but I am still getting the error

C:\Windows\System32>certutil -addstore "Root" "C:\Users\MYNAME\AppData\Roaming\Proxyman\certificate\certs\ca.pem" 
Root "Trusted Root Certification Authorities"
CertUtil: -addstore command failed. 0x80092009 (-2146885623 CRYPT_E_NO_MATCH)
CertUtil: The requested object could not be found.

Additionally, automatic certificate installation ends without any notification.

@K-4RMA commented on GitHub (Aug 15, 2025): I did a fresh install of Proxyman Version 3.0.0 (30000) | Windows (Build 10.0.26100) but I am still getting the error ``` C:\Windows\System32>certutil -addstore "Root" "C:\Users\MYNAME\AppData\Roaming\Proxyman\certificate\certs\ca.pem" Root "Trusted Root Certification Authorities" CertUtil: -addstore command failed. 0x80092009 (-2146885623 CRYPT_E_NO_MATCH) CertUtil: The requested object could not be found. ``` Additionally, automatic certificate installation ends without any notification.

kerem commented

2026-03-03 19:51:11 +03:00

Author

Owner

@kics223w1 commented on GitHub (Aug 15, 2025):

@DongjuTheDeveloper Could you please export the certificate and share it with me on GitHub? I’d like to investigate. 👍🏻
By the way, does the Install Certificate with Windows Trust Store feature work for you? 🤔

You can use the Export option in the screenshot:

@kics223w1 commented on GitHub (Aug 15, 2025): @DongjuTheDeveloper Could you please export the certificate and share it with me on GitHub? I’d like to investigate. 👍🏻 By the way, does the Install Certificate with Windows Trust Store feature work for you? 🤔 You can use the Export option in the screenshot: <img width="2200" height="1541" alt="Image" src="https://github.com/user-attachments/assets/0a29b25f-fc4e-46c9-b2ac-df5068566de0" />

kerem commented

2026-03-03 19:51:11 +03:00

Author

Owner

@K-4RMA commented on GitHub (Aug 16, 2025):

Proxyman CA.txt
This is a .pem file converted to .txt for attachment.

@K-4RMA commented on GitHub (Aug 16, 2025): [Proxyman CA.txt](https://github.com/user-attachments/files/21806840/Proxyman.CA.txt) This is a .pem file converted to .txt for attachment.

kerem commented

2026-03-03 19:51:12 +03:00

Author

Owner

@kics223w1 commented on GitHub (Aug 16, 2025):

Can you replace your certificate folder with mine and try installing the certificate automatically again? I believe this will work 👍🏻

certificate.zip

Also, the certificate that you sent me is corrupted. I’m refactoring the code that generates the certificate to make sure this won’t happen again.

@kics223w1 commented on GitHub (Aug 16, 2025): Can you replace your certificate folder with mine and try installing the certificate automatically again? I believe this will work 👍🏻 [certificate.zip](https://github.com/user-attachments/files/21812335/certificate.zip) Also, the certificate that you sent me is corrupted. I’m refactoring the code that generates the certificate to make sure this won’t happen again.

kerem commented

2026-03-03 19:51:12 +03:00

Author

Owner

@K-4RMA commented on GitHub (Aug 16, 2025):

It works! Can you tell me why this error occurred?

@K-4RMA commented on GitHub (Aug 16, 2025): It works! Can you tell me why this error occurred?

kerem commented

2026-03-03 19:51:12 +03:00

Author

Owner

@kics223w1 commented on GitHub (Aug 16, 2025):

I think the problem is with the code that generates the certificate. It doesn’t work properly on your machine, so it produces a broken certificate. This issue will be fixed in the next version.

@kics223w1 commented on GitHub (Aug 16, 2025): I think the problem is with the code that generates the certificate. It doesn’t work properly on your machine, so it produces a broken certificate. This issue will be fixed in the next version.