[GH-ISSUE #3515] [bug]: TLS 1.3 not supported in desktop app #1188

New issue

Open

opened 2026-03-16 19:02:34 +03:00 by kerem · 1 comment

kerem commented

2026-03-16 19:02:34 +03:00

Owner

Originally created by @baek-sang on GitHub (Nov 9, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3515

Is there an existing issue for this?

I have searched the existing issues

Current behavior

When using the desktop app, setting the cloudflare Minimum TLS Version to TLS 1.3 causes request errors. (Works fine if set to TLS 1.2)
However, if you use the extension in the web version, TLS1.3 will not experience any issues.

Steps to reproduce

Minimum TLS Version set TLS 1.3
Send request

Environment

Production

Version

Local

Originally created by @baek-sang on GitHub (Nov 9, 2023). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3515 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior When using the desktop app, setting the cloudflare Minimum TLS Version to TLS 1.3 causes request errors. (Works fine if set to TLS 1.2) However, if you use the extension in the web version, TLS1.3 will not experience any issues. <img width="453" alt="hops-error" src="https://github.com/hoppscotch/hoppscotch/assets/69100154/87330f34-8318-4fa1-b23d-5139723b7e57"> <img width="864" alt="cf-tls13" src="https://github.com/hoppscotch/hoppscotch/assets/69100154/475dcb78-23d6-4e23-9b54-20692fb7e7d1"> ### Steps to reproduce 1. Minimum TLS Version set TLS 1.3 2. Send request ### Environment Production ### Version Local

kerem added the

bug

need testing

desktop

labels

2026-03-16 19:02:34 +03:00

kerem commented

2026-03-16 19:02:45 +03:00

Author

Owner

@liyasthomas commented on GitHub (Sep 25, 2024):

Reopening this issue for continued tracking as it was unintentionally closed. This is still relevant for further discussion/implementation. Thank you!

@liyasthomas commented on GitHub (Sep 25, 2024): Reopening this issue for continued tracking as it was unintentionally closed. This is still relevant for further discussion/implementation. Thank you!

kerem referenced this issue

2026-03-17 00:47:22 +03:00

[PR #1220] [MERGED] Add search input & capability to graphql types and fields #3148