[GH-ISSUE #5684] [feature]: Use windows certificate store in Hoppscotch Agent and Desktop App #2206

New issue

Open

opened 2026-03-16 23:34:38 +03:00 by kerem · 3 comments

kerem commented

2026-03-16 23:34:38 +03:00

Owner

Originally created by @emil-johansson-99 on GitHub (Dec 10, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5684

Originally assigned to: @CuriousCorrelation on GitHub.

Is there an existing issue for this?

I have searched the existing issues

Summary

Change implementation in Hoppscotch Agent and Desktop App to use Windows native certificate store instead of built-in certificate store.

Why should this be worked on?

Our organization uses a VPN that introduces an internal self-signed certificate. Since most applications do not trust self-signed certificates by default it is pushed to managed devices and inserted in Windows certificate store. This makes most applications work well when using VPN.

Problem is that adding certificate to windows certificate store does not help for Hoppscotch Agent and Desktop App. Here is an example of error log written to io.hoppscotch.agent.log:
... relay::relay: Result Err(
Network {
message: "Failed to perform request",
cause: Some(
"[60] SSL peer certificate or SSH remote key was not OK (SSL certificate problem: self-signed certificate in certificate chain)",
),
},
)

From my investigations I see that Hoppcotch Agent and Desktop App uses a built-in certificate store instead of certificate store on host where applications are run. It holds for Windows and most likely Mac as well.

Workaround is to add self-signed certificate in application settings as domain override. There are at least two drawbacks:

Workaround need to be communicated to and performed by all Hoppscotch users.
Certificate needs to added as domain override for each required server. Adding it to global setting seems to break nominal certificate chains.

Originally created by @emil-johansson-99 on GitHub (Dec 10, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5684 Originally assigned to: @CuriousCorrelation on GitHub. ### Is there an existing issue for this? - [x] I have searched the existing issues ### Summary Change implementation in Hoppscotch Agent and Desktop App to use Windows native certificate store instead of built-in certificate store. ### Why should this be worked on? Our organization uses a VPN that introduces an internal self-signed certificate. Since most applications do not trust self-signed certificates by default it is pushed to managed devices and inserted in Windows certificate store. This makes most applications work well when using VPN. Problem is that adding certificate to windows certificate store does not help for Hoppscotch Agent and Desktop App. Here is an example of error log written to io.hoppscotch.agent.log: ... relay::relay: Result Err( Network { message: "Failed to perform request", cause: Some( "[60] SSL peer certificate or SSH remote key was not OK (SSL certificate problem: self-signed certificate in certificate chain)", ), }, ) From my investigations I see that Hoppcotch Agent and Desktop App uses a built-in certificate store instead of certificate store on host where applications are run. It holds for Windows and most likely Mac as well. Workaround is to add self-signed certificate in application settings as domain override. There are at least two drawbacks: - Workaround need to be communicated to and performed by all Hoppscotch users. - Certificate needs to added as domain override for each required server. Adding it to global setting seems to break nominal certificate chains.

kerem added the

feature

label

2026-03-16 23:34:38 +03:00

kerem commented

2026-03-16 23:34:49 +03:00

Author

Owner

@CuriousCorrelation commented on GitHub (Dec 10, 2025):

Thanks for the detailed write-up @emil-johansson-99! This is on our roadmap and something we want to tackle. No ETA to share at the moment, but we'll update this issue as things progress.

@CuriousCorrelation commented on GitHub (Dec 10, 2025): Thanks for the detailed write-up @emil-johansson-99! This is on our roadmap and something we want to tackle. No ETA to share at the moment, but we'll update this issue as things progress.

kerem commented

2026-03-16 23:34:54 +03:00

Author

Owner

@emil-johansson-99 commented on GitHub (Dec 10, 2025):

Thank you so much for quick feedback @CuriousCorrelation !

@emil-johansson-99 commented on GitHub (Dec 10, 2025): Thank you so much for quick feedback @CuriousCorrelation !

kerem commented

2026-03-16 23:34:59 +03:00

Author

Owner

@bittoby commented on GitHub (Feb 22, 2026):