SSL Handshake Failed on Windows 11 despite certificate installed

[brianwalczak]

Description

When trying to setup Proxyman on Windows 11, I am not able to use SSL proxying and get SSL Handshake Failed (or ERR_SSL_SERVER_CERT_BAD_FORMAT in browser) despite adding a wildcard (*) in SSL Proxying and installing the certificate properly.

Steps to Reproduce

1. Install Proxyman 3.9.0 version on Windows 11.

2. Enable the proxy and go to Certificate > Install Certificate on this Windows to install the certificate (manual or automatic).

3. Add wildcard/domain to SSL Proxying list (* or specific domain).

4. Browse HTTPS site.

Current Behavior

Traffic shows but SSL Handshake Failed in Proxyman, with an ERR_SSL_SERVER_CERT_BAD_FORMAT error in browser (this happens on Electron-based apps as well).

Expected Behavior

HTTPS traffic decrypts and the page loads properly.

Environment

• App version: v3.9.0
• Windows/Linux version: Windows 11 25H2 (26200.7840)

I can confirm the certificate is properly installed in Trusted Root Certificate Authorities and I don't have this issue with other self-signed certs like Charles Proxy.

[NghiaTranUIT]

May I ask what Browser you're using? Is it Google Chrome or Firefox?

[brianwalczak]

I'm experiencing this issue on Google Chrome and other Chromium-based browsers (ie. Edge). Seems to work perfectly on Firefox.

Here's a screenshot of the error seen on the browser:

[NghiaTranUIT]

I tested with Windows 11, 21H2 and it works fine. I'm updating to 25H2, which is your Windows version.

I have few question to investigate your issue:

1. May I ask if you installed the Root Certificate by following the Auto or Manual mode (In the Certificate Menu -> Install Certificate for Windows)?

2. Try going to Proxyman -> Certificate Menu -> Export -> PEM -> Save to your Desktop, and share with me the certificate to my email support@proxyman.com. I'd like to see what the difference is

[brianwalczak]

Sounds good. To answer your questions:

1. I installed the root certificate both manually and using the auto mode. I'm experiencing this issue in both setups.
2. Done!

[brianwalczak]

I've only been able to get it working properly on Firefox. Here are some version details of my Chrome build:

Google Chrome: 145.0.7632.117 (Official Build) (64-bit) (cohort: Stable Installs & Version Pins)
OS: Windows 11 Version 25H2 (Build 26200.7840)
JavaScript: V8 14.5.201.12

This issue is also prevalent on Microsoft Edge for me which is also based on Chromium:
Microsoft Edge: 145.0.3800.70 (Official build) (64-bit)
Chromium version: 145.0.7632.110
OS: Windows 11 Version 25H2 (Build 26200.7840)
JavaScript: V8 14.5.40.6