mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 08:45:58 +03:00
[GH-ISSUE #5321] [bug]: Unable to call collection via CLI on self-hosted deployment #2037
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#2037
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 @nderksen3 on GitHub (Aug 8, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5321
Originally assigned to: @mirarifhasan on GitHub.
Is there an existing issue for this?
Platform
Web App
Browser
Chrome
Operating System
Windows
Bug Description
What happened
When I attempted to run the CLI to run a collection on a self-hosted deployment, it came back with the error message "Please provide file of extension type .json: cme2hfrzg0001eg04kbxdwg31" even though it was a valid collection ID. I expected that it would run the collection from the self-hosted deployment.
Steps to reproduce
Screenshots
Additional details
I'm on company VPN in order to access Hoppscotch. Proxy is set to "browser" within the app, which works for me when running endpoints within the app itself.
Deployment Type
Self-hosted (on-prem deployment)
Version
CLI - version 0.23.2, App version 2025.2.1
@nderksen3 commented on GitHub (Aug 8, 2025):
Note that this is similar to issue https://github.com/hoppscotch/hoppscotch/issues/5166 , however the solution used there to set the
NODE_TLS_REJECT_UNAUTHORIZED=0environment variable did not work for me.@jamesgeorge007 commented on GitHub (Aug 8, 2025):
Hi, since your self-hosted Hoppscotch instance is behind a VPN, could you confirm whether it's reachable at the point where you're running the CLI command?
For example, does a command like
curl <your_instance_url>return a valid response?@nderksen3 commented on GitHub (Aug 8, 2025):
Yes, I ran curl against the same endpoint (e.g. the one shown in the screenshot ending in "/backend" from within the command line), and I got a 200 response.
@nderksen3 commented on GitHub (Aug 8, 2025):
The other possibility is that the CLI request is not correctly handling the SSO handshake to the server. The deployment is behind SSO for us to access with employee credentials, the curl request I made to the /backend endpoint leads to a SAML request, which in turn opens a call to our federated identity provider within the browser.
@nderksen3 commented on GitHub (Aug 26, 2025):
@jamesgeorge007 or others, any thoughts on how to resolve?
@nderksen3 commented on GitHub (Oct 3, 2025):
@mirarifhasan Looks like this is assigned to you, any thoughts? I am still unable to use CLI, which takes away a big part of the benefit I was looking for from Hoppscotch.