mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 17:26:03 +03:00
[GH-ISSUE #3872] [bug]: Unable to Connect to WebSocket #1360
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#1360
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 @ashikkabeer on GitHub (Feb 28, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3872
Is there an existing issue for this?
Current behavior
Attempting to connect to a WebSocket using Socket.IO in Hoppscotch results in a 'Failed to connect' message. However, the same configuration is successful when using Postman.
I expect the WebSocket connection to be established successfully.
Steps to reproduce
Environment
Production
Version
Local
@x-tropy commented on GitHub (May 10, 2024):
Second this. (having problem with connecting local hosted socket.io v4)
Tried chrome extension as interceptor:

Added localhost origin:

Postman is okay with this use case:

@x-tropy commented on GitHub (May 10, 2024):
I have set up the local server this way:
@Disservin commented on GitHub (Aug 30, 2024):
fyi, that is the error
saying (for dev purpose)
and then connecting to
http://localhost:3000in hoppscotch works.@ThiLourenco commented on GitHub (Sep 14, 2024):
Same problem here, I can connect, but then it disconnects.
@ThiLourenco commented on GitHub (Sep 18, 2024):
I fixed using typing
const socket = connection
@ThiLourenco commented on GitHub (Sep 18, 2024):