[GH-ISSUE #5411] [bug]: HTTPS requests to IP addresses fail due to certificate validation issues #2077

New issue

Closed

opened 2026-03-16 23:05:53 +03:00 by kerem · 0 comments

kerem commented

2026-03-16 23:05:53 +03:00

Owner

Originally created by @Sunlery on GitHub (Sep 29, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5411

Is there an existing issue for this?

I have searched existing issues and this bug hasn't been reported yet

Platform

Desktop App

Browser

Edge

Operating System

Windows

Bug Description

Description

When attempting to make HTTPS requests to an IP address (e.g., https://192.168.1.100), Hoppscotch fails to complete the request due to SSL certificate validation errors. This is a common scenario in local development, internal networks, or IoT environments where services are exposed via IP rather than a domain name.

Steps to Reproduce

Open Hoppscotch.
Enter an HTTPS URL pointing directly to an IP address, for example:
```
https://192.168.1.100/api/test
```
Send the request.
Observe that the request fails.

Expected Behavior

Hoppscotch should either:
- Allow users to bypass SSL certificate validation for IP-based HTTPS URLs.
- Support trusting self-signed or manually uploaded certificates for IP addresses.
- Provide a clear error message indicating that the failure is due to certificate validation and suggest next steps.

Actual Behavior

The request fails with a generic error message or no response.
There is no indication that the failure is related to SSL certificate validation for the IP address.

Screenshots / Logs

If applicable, attach screenshots of the error or browser console logs.

Environment

Hoppscotch version: 25.8.1.0
OS: Windows 11

Additional Notes

In development and internal environments, it is common to expose services via IP addresses with self-signed certificates. Supporting this use case would make Hoppscotch more versatile for developers and system administrators.

Deployment Type

Hoppscotch Cloud

Version

No response

Originally created by @Sunlery on GitHub (Sep 29, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5411 ### Is there an existing issue for this? - [x] I have searched existing issues and this bug hasn't been reported yet ### Platform Desktop App ### Browser Edge ### Operating System Windows ### Bug Description ### Description When attempting to make HTTPS requests to an IP address (e.g., `https://192.168.1.100`), Hoppscotch fails to complete the request due to SSL certificate validation errors. This is a common scenario in local development, internal networks, or IoT environments where services are exposed via IP rather than a domain name. ### Steps to Reproduce 1. Open Hoppscotch. 2. Enter an HTTPS URL pointing directly to an IP address, for example: ``` https://192.168.1.100/api/test ``` 3. Send the request. 4. Observe that the request fails. <img width="1278" height="903" alt="Image" src="https://github.com/user-attachments/assets/599be113-c6b1-46e1-b887-4b35d0c1c560" /> #### Expected Behavior - Hoppscotch should either: - Allow users to bypass SSL certificate validation for IP-based HTTPS URLs. - Support trusting self-signed or manually uploaded certificates for IP addresses. - Provide a clear error message indicating that the failure is due to certificate validation and suggest next steps. #### Actual Behavior - The request fails with a generic error message or no response. - There is no indication that the failure is related to SSL certificate validation for the IP address. #### Screenshots / Logs If applicable, attach screenshots of the error or browser console logs. #### Environment - Hoppscotch version: 25.8.1.0 - OS: Windows 11 #### Additional Notes In development and internal environments, it is common to expose services via IP addresses with self-signed certificates. Supporting this use case would make Hoppscotch more versatile for developers and system administrators. --- ### Deployment Type Hoppscotch Cloud ### Version _No response_