mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #5003] [bug]:The desktop application cannot access the local API. #1905
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#1905
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @shixing2 on GitHub (Apr 17, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5003
Is there an existing issue for this?
Current behavior
In Windows 11, I want to access the local api, but it doesn't work. None of the options are working.
Steps to reproduce
Logs and Screenshots
Environment
Production
Hoppscotch Version
Local
Interceptor
Native - Desktop App
Browsers Affected
Not applicable (Desktop app)
Operating System
Windows
Additional Information
No response
@shixing2 commented on GitHub (Apr 17, 2025):
@CuriousCorrelation commented on GitHub (Apr 17, 2025):
Hi @shixing2, could you please add a title for the bug report that summarizes the situation you are experiencing? Empty titles are difficult to track.
As I understand, you appear to be using both Hoppscotch Desktop app and Hoppscotch Agent simultaneously, which isn't the intended configuration. The Hoppscotch Agent is specifically designed to work with the Hoppscotch Web app, not the desktop app. The desktop app already has built-in capabilities via “Native” interceptor that make the Agent unnecessary. The docs provide a great walkthrough on these distributions.
I also notice you're trying to use a proxy to connect to the endpoint, but the proxy field appears to be empty in your settings page screenshot. If you don't actually need to proxy the requests, it is recommended to disable this option using the toggle shown above the field.
I'm also seeing that you aren't connecting to a local server but rather a server hosted on a domain, so unsure as to what you meant by "access to local api".
Could you clarify these with some more details about what you're specifically trying to accomplish? This would help a lot in determining the exact issue. Thanks!
@shixing2 commented on GitHub (Apr 17, 2025):
desktop application cannot access the local API.
the same API can be successfully requested in Google Chrome.
What configuration is causing this issue?
@CuriousCorrelation commented on GitHub (Apr 17, 2025):
Thanks for the update. The settings seems to be set correctly, although status code
502can sometimes mean an issue with domain resolution. Could you please check if the generatedcURLrequest is able to correctly connect to the server?Here's an example of a
GETrequest tohttps://echo.hoppscotch.io@shixing2 commented on GitHub (Apr 17, 2025):
test result.
Google Chrome request result
test results using other tools
@CuriousCorrelation commented on GitHub (Apr 17, 2025):
Thanks for running the diagnostics! This doesn't appear to be a resolution issue, let's investigate how the request is being handled differently between the two clients.
Could you help me:
https://echo.hoppscotch.iousing both Web app and the desktop app with identical parameters and sharing the response? This would help a lot to understand the differences in how requests are being formed, transmitted and received. You can simply change the URL and keep everything as is to run this test.@shixing2 commented on GitHub (Apr 18, 2025):
Thank you, please see the test results.
@CuriousCorrelation commented on GitHub (Apr 18, 2025):
Hi @shixing2, thanks for the info!
I’m finding it a bit difficult to replicate this on my machine, even with setting up a local server with custom host files. All requests seems to be going through correctly. So perhaps this is an environment specific issue that is affecting native request calls.
The 502 Bad Gateway in some cases points to an internal proxy/gateway in the app's communication path still, where it’s receiving invalid response from an upstream server.
A workaround to try first would be using the direct IP address instead of the domain name, like so
http://192.168.174.133:80/credit/v2/creditApplywhich might bypass potential domain handling issues.No worries if that doesn't work, I'm working on a log rotation system for the desktop app that will provide much better insights into the communication path. This should be available in one of the upcoming releases and will definitely accelerate diagnosis of issues like this in the future.
@CuriousCorrelation commented on GitHub (Apr 30, 2025):
Hello @shixing2, the latest update for the desktop app (v25.4.0) now includes file-based rotating logs, a feature specifically implemented to help diagnose environment-specific issues like the one you were experiencing.
If you're still experiencing this issue after trying the IP address workaround, please update to the latest version (v25.4.0) and if you can, share your anonymized logs here.
The log files are located at:
C:\Users\<username>\AppData\Local\io.hoppscotch.desktop\logs\io.hoppscotch.desktop.log~/Library/Logs/io.hoppscotch.desktop/io.hoppscotch.desktop.log~/.local/share/io.hoppscotch.desktop/logs/io.hoppscotch.desktop.logFor more info on this logging feature, see PR https://github.com/hoppscotch/hoppscotch/pull/5009