starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-25 16:55:59 +03:00

[GH-ISSUE #1614] Websocket (socket.io) not connecting #509

New issue

Closed

opened 2026-03-16 15:46:06 +03:00 by kerem · 10 comments

kerem commented

2026-03-16 15:46:06 +03:00

Owner

Originally created by @AllanOricil on GitHub (Apr 22, 2021).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/1614

Originally assigned to: @blenderskool on GitHub.

Describe the bug
I have a websocket running alongside an express app and when I click "connect" in hoppscotch it displays an error message, but in the express side I can see a "connected" log displayed. So it means hoppscotch is hitting the websocket but it fails to retain the connection

Express Log

To Reproduce
Steps to reproduce the behavior:

Attach a websocket using socket.io in an express app
Open hoppscotch and hit "connect"

Expected behavior
It should connect

Screenshots
It is not connecting

Desktop (please complete the following information):

OS: Windows 10

Additional context
Express App dependencies

"dependencies": {
"@types/vscode": "^1.53.0",
"applicationinsights": "^1.8.2",
"axios": "^0.21.1",
"cors": "^2.8.5",
"dateformat": "^4.5.1",
"dotenv": "^8.2.0",
"express": "^4.17.1",
"fs-extra": "^9.0.1",
"jsforce": "^2.0.0-beta.3",
"morgan-body": "^2.6.4",
"node-machine-id": "^1.1.12",
"objects-to-csv": "^1.3.6",
"open": "^8.0.2",
"qs": "^6.9.4",
"rotating-file-stream": "^2.1.3",
"socket.io": "^2.4.1"
}

Originally created by @AllanOricil on GitHub (Apr 22, 2021). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/1614 Originally assigned to: @blenderskool on GitHub. **Describe the bug** I have a websocket running alongside an express app and when I click "connect" in hoppscotch it displays an error message, but in the express side I can see a "connected" log displayed. So it means hoppscotch is hitting the websocket but it fails to retain the connection ![image](https://user-images.githubusercontent.com/55927613/115769089-0ee7c880-a3a3-11eb-99ae-9bfada26f2e4.png) Express Log ![image](https://user-images.githubusercontent.com/55927613/115769190-2c1c9700-a3a3-11eb-9d5d-67497e4160d8.png) **To Reproduce** Steps to reproduce the behavior: 1. Attach a websocket using socket.io in an express app 2. Open hoppscotch and hit "connect" **Expected behavior** It should connect **Screenshots** It is not connecting **Desktop (please complete the following information):** - OS: Windows 10 **Additional context** Express App dependencies "dependencies": { "@types/vscode": "^1.53.0", "applicationinsights": "^1.8.2", "axios": "^0.21.1", "cors": "^2.8.5", "dateformat": "^4.5.1", "dotenv": "^8.2.0", "express": "^4.17.1", "fs-extra": "^9.0.1", "jsforce": "^2.0.0-beta.3", "morgan-body": "^2.6.4", "node-machine-id": "^1.1.12", "objects-to-csv": "^1.3.6", "open": "^8.0.2", "qs": "^6.9.4", "rotating-file-stream": "^2.1.3", "socket.io": "^2.4.1" }

kerem

2026-03-16 15:46:06 +03:00

closed this issue
added the
good first issue

need testing

hacktoberfest
labels

kerem commented

2026-03-16 15:46:22 +03:00

Author

Owner

@AllanOricil commented on GitHub (Apr 22, 2021):

This other tool connects without a problem. Maybe it is because you are using socket.io 3? If so, there should be an option to choose socket.io version

@AllanOricil commented on GitHub (Apr 22, 2021): This other tool connects without a problem. Maybe it is because you are using socket.io 3? If so, there should be an option to choose socket.io version ![image](https://user-images.githubusercontent.com/55927613/115771416-cda4e800-a3a5-11eb-9e02-e0a79be2ad90.png)

kerem commented

2026-03-16 15:46:28 +03:00

Author

Owner

@liyasthomas commented on GitHub (Apr 22, 2021):

Thanks for reporting the issue. We'll take a look at it and get back to you.

@liyasthomas commented on GitHub (Apr 22, 2021): Thanks for reporting the issue. We'll take a look at it and get back to you.

kerem commented

2026-03-16 15:46:33 +03:00

Author

Owner

@AllanOricil commented on GitHub (Apr 23, 2021):

I think you will have three builds one for each socketio client version (2,3 4) and then give the option for the user to switch between them. You can have routes like

../socketio/3
../socketio/2
../socketio/4

Then on your dns you configure a CNAME for each build when the user reaches that particular route. The downside I see is that it will require a page reload :/

@AllanOricil commented on GitHub (Apr 23, 2021): I think you will have three builds one for each socketio client version (2,3 4) and then give the option for the user to switch between them. You can have routes like ../socketio/3 ../socketio/2 ../socketio/4 Then on your dns you configure a CNAME for each build when the user reaches that particular route. The downside I see is that it will require a page reload :/

kerem commented

2026-03-16 15:46:38 +03:00

Author

Owner

@AllanOricil commented on GitHub (Apr 23, 2021):

Oh I just found that we can have multiple versions of the same dependency using aliases. I just don't know if the imports will use the aliases or the lib.

@AllanOricil commented on GitHub (Apr 23, 2021): Oh I just found that we can have multiple versions of the same dependency using aliases. I just don't know if the imports will use the aliases or the lib.

kerem commented

2026-03-16 15:47:22 +03:00

Author

Owner

@blenderskool commented on GitHub (Oct 1, 2021):

@liyasthomas Can I experiment and try working on this?

@blenderskool commented on GitHub (Oct 1, 2021): @liyasthomas Can I experiment and try working on this?

kerem commented

2026-03-16 15:47:28 +03:00

Author

Owner

@liyasthomas commented on GitHub (Oct 1, 2021):

Hi @blenderskool, you're free to take a shot at this. Am assigning this issue to you, do let us know if you need any help understanding the codebase.

@liyasthomas commented on GitHub (Oct 1, 2021): Hi @blenderskool, you're free to take a shot at this. Am assigning this issue to you, do let us know if you need any help understanding the codebase.

kerem commented

2026-03-16 15:47:33 +03:00

Author

Owner

@blenderskool commented on GitHub (Oct 11, 2021):

@liyasthomas So I tried recreating the issue, and below are my findings:

Hoppscotch is using socket.io-client v4, and based on the compatibility chart, we cannot connect to servers running socket.io v2.
Also looking at the compatibility chart, socket.io-client v2 seems to widely support connecting to different versions of socket.io server, so we may try downgrading to that version on Hoppscotch and make appropriate changes.
The other option is that we show some kind of menu to users for selecting the socket.io-client version they'd prefer using, as @AllanOricil mentioned.

@blenderskool commented on GitHub (Oct 11, 2021): @liyasthomas So I tried recreating the issue, and below are my findings: - Hoppscotch is using socket.io-client v4, and based on the [compatibility chart](https://socket.io/docs/v4/client-installation/), we cannot connect to servers running socket.io v2. - Also looking at the compatibility chart, socket.io-client v2 seems to widely support connecting to different versions of socket.io server, so we may try downgrading to that version on Hoppscotch and make appropriate changes. - The other option is that we show some kind of menu to users for selecting the socket.io-client version they'd prefer using, as @AllanOricil mentioned.

kerem commented

2026-03-16 15:47:38 +03:00

Author

Owner

@liyasthomas commented on GitHub (Oct 11, 2021):

I'm not sure of if the imports supports multiple versions of the same package.

@liyasthomas commented on GitHub (Oct 11, 2021): I'm not sure of if the imports supports multiple versions of the same package.

kerem commented

2026-03-16 15:47:43 +03:00

Author

Owner

@blenderskool commented on GitHub (Oct 11, 2021):

@liyasthomas It might be possible via aliases. I'm not sure if this is a good idea if we are concerned about bundle sizes.

@blenderskool commented on GitHub (Oct 11, 2021): @liyasthomas It might be possible via [aliases](https://pnpm.io/aliases). I'm not sure if this is a good idea if we are concerned about bundle sizes.

kerem commented

2026-03-16 15:47:48 +03:00

Author

Owner

@abishekpp commented on GitHub (Jul 19, 2025):

still not solved

@abishekpp commented on GitHub (Jul 19, 2025): still not solved

kerem referenced this issue

2026-03-17 00:21:08 +03:00

[PR #510] [MERGED] Validate duplicate collections #2666