RocketChat / RocketChat/Rocket.Chat
RocketChat container behind Nginx reverse proxy cannot access with error: "POST https://192.168.1.6:8066/meteor/dynamic-import/fetch net::ERR_CONNECTION_CLOSED"
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
After I've upgrade to RocketChat version 6.0 to 6.4.2, RocketChat container behind Nginx reverse proxy cannot access with error: "POST https://192.168.1.6:8066/meteor/dynamic-import/fetch net::ERR_CONNECTION_CLOSED"
Environment Information:
- Rocket.Chat Server Version: rocketchat/rocket.chat:6.4.2 (Docker container)
- Rocket.Chat App Version: 6.4.2
- Device Name: Chrome
- OS Version: Debian GNU/Linux 11 (bullseye) (Docker container)
Steps to reproduce:
- Install RocketChat in a Docker container.
- Configure Nginx as a reverse proxy for RocketChat.
- Try to access RocketChat using the Nginx reverse proxy URL.
Expected behavior:
RocketChat should load successfully.
Actual behavior:
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 by reproducing Rocket.Chat 6.4.2 in the rocketchat/rocket.chat Docker container behind the reported Nginx reverse proxy, then inspect the failing POST to /meteor/dynamic-import/fetch and its connection logs. Done means the application loads successfully through the reverse-proxy URL without ERR_CONNECTION_CLOSED.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, nginx
- Domain
- devops, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100