starred/proxyman-windows-linux
1
0
Fork 0
mirror of https://github.com/ProxymanApp/proxyman-windows-linux.git synced 2026-04-27 00:45:55 +03:00
Code Issues 541 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #577] SSL Handshake Failed on Windows 11 despite certificate installed #572

New issue
Open
opened 2026-03-03 19:51:23 +03:00 by kerem · 5 comments
kerem commented 2026-03-03 19:51:23 +03:00
Owner
Copy link

Originally created by @brianwalczak on GitHub (Feb 23, 2026).
Original GitHub issue: https://github.com/ProxymanApp/proxyman-windows-linux/issues/577

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.

Originally created by @brianwalczak on GitHub (Feb 23, 2026). Original GitHub issue: https://github.com/ProxymanApp/proxyman-windows-linux/issues/577 ## 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.
kerem commented 2026-03-03 19:51:24 +03:00
Author
Owner
Copy link

@NghiaTranUIT commented on GitHub (Feb 23, 2026):

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

<!-- gh-comment-id:3945988635 --> @NghiaTranUIT commented on GitHub (Feb 23, 2026): May I ask what Browser you're using? Is it Google Chrome or Firefox?
kerem commented 2026-03-03 19:51:24 +03:00
Author
Owner
Copy link

@brianwalczak commented on GitHub (Feb 23, 2026):

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:

Image
<!-- gh-comment-id:3947484326 --> @brianwalczak commented on GitHub (Feb 23, 2026): 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: <img width="546" height="262" alt="Image" src="https://github.com/user-attachments/assets/51d313ad-c829-43f1-9e60-b263509b367f" />
kerem commented 2026-03-03 19:51:24 +03:00
Author
Owner
Copy link

@NghiaTranUIT commented on GitHub (Feb 24, 2026):

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

Image

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)?
Image
  1. 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
<!-- gh-comment-id:3948255384 --> @NghiaTranUIT commented on GitHub (Feb 24, 2026): I tested with Windows 11, 21H2 and it works fine. I'm updating to 25H2, which is your Windows version. <img width="1727" height="1071" alt="Image" src="https://github.com/user-attachments/assets/03ec7629-6f19-451a-b8eb-5bc1d2f1fd54" /> 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)? <img width="933" height="434" alt="Image" src="https://github.com/user-attachments/assets/6aa31ac1-e108-493d-a321-962bb6308110" /> 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
kerem commented 2026-03-03 19:51:24 +03:00
Author
Owner
Copy link

@brianwalczak commented on GitHub (Feb 24, 2026):

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!
Image
<!-- gh-comment-id:3948380406 --> @brianwalczak commented on GitHub (Feb 24, 2026): 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! <img width="648" height="265" alt="Image" src="https://github.com/user-attachments/assets/60d53bd8-2211-4219-bab7-86aac244923a" />
kerem commented 2026-03-03 19:51:24 +03:00
Author
Owner
Copy link

@brianwalczak commented on GitHub (Feb 24, 2026):

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

<!-- gh-comment-id:3948455213 --> @brianwalczak commented on GitHub (Feb 24, 2026): 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
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
feat/new-version
3.12.0
3.11.0
3.10.0
3.4.0
3.5.0
3.6.0
3.7.0
3.8.0
3.9.0
3.3.0
2.25.0
2.24.0
3.2.0
3.0.0
3.1.0
2.26.0
2.27.0
2.23.0
2.22.0
2.21.0
2.20.0
2.19.0
2.18.0
2.17.0
2.16.0
2.15.0
2.14.0
2.13.0
2.12.0
2.11.1
2.11.0
2.10.0
2.9.0
2.8.0
2.7.0
2.6.0
2.5.0
2.4.0
2.3.0
1.9.2
2.0.0
1.9.1
1.8.1
1.9.0
1.8.0
1.7.0
1.6.0
1.5.0
1.4.0
1.3.0
1.2.0
1.1.0
1.0.0
0.10.0
0.9.0
0.8.0
0.6.0
0.5.0
0.4.2
0.4.1
0.4.0
0.3.0
0.1.1
0.2.0
0.1.0
Labels
Clear labels   
Linux

   
bug

   
enhancement

   
enhancement

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
✅ Done
No labels
Linux
bug
enhancement
enhancement
pull-request
question
✅ Done
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/proxyman-windows-linux#572
No description provided.