[GH-ISSUE #5203] [bug]: Unable to Route API Requests Through Proxy - Burp Suite – "Network Connection Failed" Error in Desktop App #1984

Closed
opened 2026-03-16 22:45:36 +03:00 by kerem · 5 comments
Owner

Originally created by @mithu36 on GitHub (Jun 26, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5203

Is there an existing issue for this?

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

Platform

Desktop App

Browser

Chrome

Operating System

Windows

Bug Description

Issue:

My Requirement is to capture all API request going from hoppscotch in burpsuite. so i created a proxy in burpsuite 127.0.0.1:8080 and added the same in Hoppscotch also. but after adding the proxy for all request it is showing Network connection failed. proxy request failed error.

Steps to reproduce:

  • Open Burpsuite
  • Navigate to Proxy -> Proxy seeting
  • Add address 127.0.0.1 and port 8080 (you can use any other port also)
  • The open Hoppscotch Desktop application
  • Navigate to Settings -> Proxy
  • In proxy add http://127.0.0.1:8080/ or 127.0.0.1:8080
  • Then request to any API or website you will see Network connection failed

POC

Proxy on Burpsuite
Image

Proxy added on Hoppscotch
Image

Tried adding Proxy under the first part also on Hoppscotch where we setup username and pass
Image

Getting network errror

Image

Deployment Type

Self-hosted (on-prem deployment)

Version

V2025.5.4

Originally created by @mithu36 on GitHub (Jun 26, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5203 ### 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 Chrome ### Operating System Windows ### Bug Description **Issue:** My Requirement is to capture all API request going from hoppscotch in burpsuite. so i created a proxy in burpsuite 127.0.0.1:8080 and added the same in Hoppscotch also. but after adding the proxy for all request it is showing Network connection failed. proxy request failed error. **Steps to reproduce:** - Open Burpsuite - Navigate to Proxy -> Proxy seeting - Add address 127.0.0.1 and port 8080 _(you can use any other port also)_ - The open Hoppscotch Desktop application - Navigate to Settings -> Proxy - In proxy add http://127.0.0.1:8080/ or 127.0.0.1:8080 - Then request to any API or website you will see Network connection failed POC **Proxy on Burpsuite** <img width="352" alt="Image" src="https://github.com/user-attachments/assets/a93c2fc1-97e5-44ae-9f2e-25b0aa53ace3" /> **Proxy added on Hoppscotch** <img width="490" alt="Image" src="https://github.com/user-attachments/assets/7510c353-01b6-4e32-b48c-d222d00834ba" /> **Tried adding Proxy under the first part also on Hoppscotch where we setup username and pass** <img width="476" alt="Image" src="https://github.com/user-attachments/assets/c95703ae-bf6b-4966-9982-e1ca96e0eace" /> **Getting network errror** <img width="629" alt="Image" src="https://github.com/user-attachments/assets/7b16f37d-2685-48d7-bde2-fddadeafcace" /> ### Deployment Type Self-hosted (on-prem deployment) ### Version V2025.5.4
kerem 2026-03-16 22:45:36 +03:00
Author
Owner

@CuriousCorrelation commented on GitHub (Jun 26, 2025):

Hi @mithu36, the "Proxy" interceptor is specifically for routing requests through Proxyscotch (a separate proxy server), not for configuring general proxy settings. You can read more about interceptors in our documentation.

For your use case, you'll want to use the "Native" interceptor with proxy configuration instead:

Navigate to Settings page -> scroll down and select Native -> enable Proxy toggle just like you did before

Image

and input your configs in that section.

Once that's done, retry sending the request. Let me know if this resolves the issue for you.

<!-- gh-comment-id:3007992444 --> @CuriousCorrelation commented on GitHub (Jun 26, 2025): Hi @mithu36, the "Proxy" interceptor is specifically for routing requests through [Proxyscotch](https://github.com/hoppscotch/proxyscotch) (a separate proxy server), not for configuring general proxy settings. You can read more about interceptors in our [documentation](https://docs.hoppscotch.io/documentation/features/interceptor). For your use case, you'll want to use the "Native" interceptor with proxy configuration instead: Navigate to `Settings` page -> scroll down and select `Native` -> enable `Proxy` toggle just like you did before ![Image](https://github.com/user-attachments/assets/40b5419a-193c-4307-95cf-bd19839b3daa) and input your configs in that section. Once that's done, retry sending the request. Let me know if this resolves the issue for you.
Author
Owner

@mithu36 commented on GitHub (Jun 26, 2025):

Hi,
I tried that also.. but again same network error.
In Native if i didn't give proxy 127.0.0.1:8080 it will work but my requirement is to get all in burpsuite so if i add the proxy then it is giving Network error

Image

network error

Image
<!-- gh-comment-id:3008018223 --> @mithu36 commented on GitHub (Jun 26, 2025): Hi, I tried that also.. but again same network error. In **Native** if i didn't give proxy 127.0.0.1:8080 it will work but my requirement is to get all in burpsuite so if i add the proxy then it is giving Network error <img width="713" alt="Image" src="https://github.com/user-attachments/assets/911bc895-f873-40e0-9d38-41092546c843" /> **network error** <img width="638" alt="Image" src="https://github.com/user-attachments/assets/9d37f3c2-fac8-4bc9-bddf-cbbf66c6647d" />
Author
Owner

@CuriousCorrelation commented on GitHub (Jun 26, 2025):

Hi @mithu36, the SSL certificate error you're seeing is expected when using Burp as an intercepting proxy. In your Native interceptor settings, you have "Verify Host" and "Verify Peer" toggled on.

You can turn off the "Verify Host" and "Verify Peer" toggles for the quickest solution. Alternatively, you can use the "CA Certificates" section in your settings to upload Burp's CA certificate.

Let me know if turning off those two toggles resolves the issue.

<!-- gh-comment-id:3008052488 --> @CuriousCorrelation commented on GitHub (Jun 26, 2025): Hi @mithu36, the SSL certificate error you're seeing is expected when using Burp as an intercepting proxy. In your Native interceptor settings, you have "Verify Host" and "Verify Peer" toggled on. You can turn off the "Verify Host" and "Verify Peer" toggles for the quickest solution. Alternatively, you can use the "CA Certificates" section in your settings to upload Burp's CA certificate. Let me know if turning off those two toggles resolves the issue.
Author
Owner

@mithu36 commented on GitHub (Jun 26, 2025):

Hi @CuriousCorrelation I turned off those two toggles and it is working now.

Thank you for your quick response.! Issue solved

<!-- gh-comment-id:3008111285 --> @mithu36 commented on GitHub (Jun 26, 2025): Hi @CuriousCorrelation I turned off those two toggles and it is working now. Thank you for your quick response.! Issue solved
Author
Owner

@CuriousCorrelation commented on GitHub (Jun 26, 2025):

Excellent @mithu36 🚀

Glad I could help!

<!-- gh-comment-id:3008114454 --> @CuriousCorrelation commented on GitHub (Jun 26, 2025): Excellent @mithu36 🚀 Glad I could help!
Sign in to join this conversation.
No milestone
No project
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/hoppscotch#1984
No description provided.