[GH-ISSUE #2896] [bug]: Only able to access echo.hoppscotch.io when using docker #936

New issue

Closed

opened 2026-03-16 17:44:39 +03:00 by kerem · 3 comments

kerem commented

2026-03-16 17:44:39 +03:00

Owner

Originally created by @WayneNani on GitHub (Jan 5, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2896

Is there an existing issue for this?

I have searched the existing issues

Current behavior

When I create a new docker container with docker run --rm --name hoppscotch -p 3000:3000 hoppscotch/hoppscotch:latest it will create the local version of hoppscotch with no problems. I can also connect to it and get a response from echo.hoppscotch.io, but as soon as I try to access a different URL (i.e. hoppscotch.io) it will fail with "Request could not be sent. API endpoint is not available" which of course should not be an issue.

Steps to reproduce

execute docker run --rm --name hoppscotch -p 3000:3000 hoppscotch/hoppscotch:latest
Go to localhost:3000
Try to access hoppscotch.io

Environment

Production

Version

Self-hosted

Originally created by @WayneNani on GitHub (Jan 5, 2023). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2896 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior When I create a new docker container with `docker run --rm --name hoppscotch -p 3000:3000 hoppscotch/hoppscotch:latest` it will create the local version of hoppscotch with no problems. I can also connect to it and get a response from echo.hoppscotch.io, but as soon as I try to access a different URL (i.e. hoppscotch.io) it will fail with "Request could not be sent. API endpoint is not available" which of course should not be an issue. ### Steps to reproduce 1. execute `docker run --rm --name hoppscotch -p 3000:3000 hoppscotch/hoppscotch:latest` 2. Go to localhost:3000 3. Try to access hoppscotch.io ![grafik](https://user-images.githubusercontent.com/32562853/210819234-4f5008ab-78e5-4150-8006-ff554f92731a.png) ### Environment Production ### Version Self-hosted

kerem

2026-03-16 17:44:39 +03:00

closed this issue
added the
bug

need testing
labels

kerem commented

2026-03-16 17:44:55 +03:00

Author

Owner

@AndrewBastin commented on GitHub (Jan 6, 2023):

This is an expected behaviour.
You can fix this by installing the Hoppscotch browser extension and adding your container URL (in your case localhost:3000). Then you can use "Browser Extension" on the interceptor menu.

Alternatively you can also self host Proxyscotch if you want to run it as a proxy.

Do let me know if you need more help or if this fixed your issue, please close this ticket!

@AndrewBastin commented on GitHub (Jan 6, 2023): This is an expected behaviour. You can fix this by installing the Hoppscotch browser extension and adding your container URL (in your case `localhost:3000`). Then you can use "Browser Extension" on the interceptor menu. Alternatively you can also self host [Proxyscotch](https://github.com/hoppscotch/proxyscotch) if you want to run it as a proxy. Do let me know if you need more help or if this fixed your issue, please close this ticket!

kerem commented

2026-03-16 17:45:00 +03:00

Author

Owner

@WayneNani commented on GitHub (Jan 6, 2023):

This solved the issue, thank you. Could you explain shortly why this is necessary, or point me to resources explaining it? I was under the impression that hoppscotch should work "out of the box" when I run the container.

@WayneNani commented on GitHub (Jan 6, 2023): This solved the issue, thank you. Could you explain shortly why this is necessary, or point me to resources explaining it? I was under the impression that hoppscotch should work "out of the box" when I run the container.

kerem commented

2026-03-16 17:45:05 +03:00

Author

Owner

@AndrewBastin commented on GitHub (Jan 6, 2023):

@WayneNani this is a client side limitation. The current container we provide is fully client side (which means its just a static site rendered on the browser). The browser has a security policy called CORS (read more here: https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) which restricts Hoppscotch's ability to send requests to certain domains.

The extension provides a workaround from CORS just for Hoppscotch to send requests on without issues.

Since your problem was solved, I am marking this issue as closed.

@AndrewBastin commented on GitHub (Jan 6, 2023): @WayneNani this is a client side limitation. The current container we provide is fully client side (which means its just a static site rendered on the browser). The browser has a security policy called CORS (read more here: https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) which restricts Hoppscotch's ability to send requests to certain domains. The extension provides a workaround from CORS just for Hoppscotch to send requests on without issues. Since your problem was solved, I am marking this issue as closed.

kerem referenced this issue

2026-03-17 00:36:48 +03:00

[PR #936] [MERGED] ⬆️ Bump graphql-language-service-interface from 2.3.3 to 2.4.0 #2952