RocketChat / RocketChat/Rocket.Chat
This request has been blocked; this endpoint must be available over WSS. i.connect @ Connection.ts:134 Connection.ts:134
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Connection.ts:134 Mixed Content: The page at 'https://speak.mysite.com/livechat' was loaded over HTTPS, but attempted to connect to the insecure WebSocket endpoint 'ws://<IP>:3000/websocket'. This request has been blocked; this endpoint must be available over WSS.
i.connect @ Connection.ts:134
Connection.ts:134
The app is running against a subdomain like chat.mysite.com
But when I access chat.mysite.com/live chat the above errors displays in the browser console.
Facts:
- Ifram is is enabled
- Runnig over https
- Ubuntu/Docker
- Browser=(chrome, FF, Brave)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at Connection.ts:134 and reproduce the mixed-content error while loading the HTTPS iframe at /livechat. Review how the Docker/Ubuntu deployment exposes the WebSocket endpoint and whether it is configured for WSS. Done means the HTTPS page connects without the browser blocking the WebSocket request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, typescript, ubuntu
- Domain
- networking, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100