starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-26 01:06:00 +03:00

[GH-ISSUE #3890] [bug]: Error when connecting to local WebSocket endpoint #1367

New issue

Closed

opened 2026-03-16 20:00:28 +03:00 by kerem · 5 comments

kerem commented

2026-03-16 20:00:28 +03:00

Owner

Originally created by @mathaimon on GitHub (Mar 11, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3890

Is there an existing issue for this?

I have searched the existing issues

Current behavior

While trying to connect to a local WebSocket endpoint i get get and error saying that ws:// cannot be accessed because the page was loaded over HTTPS.

Steps to reproduce

Go to Realtime -> Websocket
Connect to local websocket server

Environment

Production

Version

Local

Originally created by @mathaimon on GitHub (Mar 11, 2024). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3890 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior While trying to connect to a local WebSocket endpoint i get get and error saying that ws:// cannot be accessed because the page was loaded over HTTPS. ![image](https://github.com/hoppscotch/hoppscotch/assets/64730205/ef6e12c0-fc71-4dc0-9011-4ec31a7c9ce0) ### Steps to reproduce 1. Go to Realtime -> Websocket 2. Connect to local websocket server ### Environment Production ### Version Local

kerem

2026-03-16 20:00:28 +03:00

closed this issue
added the
bug

need testing
labels

kerem commented

2026-03-16 20:00:44 +03:00

Author

Owner

@liyasthomas commented on GitHub (Mar 11, 2024):

Can you try the WSS protocol instead of WS and see if the issue persists?

@liyasthomas commented on GitHub (Mar 11, 2024): Can you try the `WSS` protocol instead of `WS` and see if the issue persists?

kerem commented

2026-03-16 20:00:49 +03:00

Author

Owner

@mathaimon commented on GitHub (Mar 11, 2024):

It works fine while using WSS.

@mathaimon commented on GitHub (Mar 11, 2024): It works fine while using `WSS`.

kerem commented

2026-03-16 20:00:55 +03:00

Author

Owner

@liyasthomas commented on GitHub (Mar 11, 2024):

The prefixes wss:// indicate that the connection is secured using TLS/SSL encryption. The prefixes ws:// indicate the connection is unsecured.

As of now, Hoppscotch requires secured API endpoints for its testing playground.

Feel free to create another issue ticket if anything goes wrong.

@liyasthomas commented on GitHub (Mar 11, 2024): The prefixes `wss://` indicate that the connection is secured using TLS/SSL encryption. The prefixes `ws://` indicate the connection is unsecured. As of now, Hoppscotch requires secured API endpoints for its testing playground. Feel free to create another issue ticket if anything goes wrong.

kerem commented

2026-03-16 20:01:00 +03:00

Author

Owner

@mathaimon commented on GitHub (Mar 11, 2024):

is there any way that i can use hoppscotch to test local ws endpoints without ssl.

@mathaimon commented on GitHub (Mar 11, 2024): is there any way that i can use hoppscotch to test local `ws` endpoints without ssl.

kerem commented

2026-03-16 20:01:05 +03:00

Author

Owner

@mathaimon commented on GitHub (Mar 11, 2024):

Also its not mentioned in the docs. https://docs.hoppscotch.io/documentation/getting-started/realtime/websocket

@mathaimon commented on GitHub (Mar 11, 2024): Also its not mentioned in the docs. https://docs.hoppscotch.io/documentation/getting-started/realtime/websocket

kerem referenced this issue

2026-03-17 00:53:52 +03:00

[PR #1367] [MERGED] Collections and environments + GitHub gist #3270