RocketChat / RocketChat/Rocket.Chat
Subdir routing is duplicated.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
As per title, I've met problem with latest image after recreating whole setup. Web applications is not responding. Proxy response is 504 Gateway Time-out. Same when i try go directly to server.
Desktop app is working like a charm.
Server Setup Information:
- Version of Rocket.Chat Server: 0.62.2
- Operating System: Debian jessie
- Deployment Method(snap/docker/tar/etc): docker
- Number of Running Instances: 1
- DB Replicaset Oplog: enabled
- Node Version:
- mongoDB Version:
Our setup has NGINX reverse proxy with these lines in config:
location /rocket{
proxy_pass http://machine-ip:3000;
}
docker compose have this:
rocketchat:
image: rocket.chat:latest
restart: unless-stopped
volumes:
- ./uploads:/app/uploads
environment:
- PORT=3000
- ROOT_URL=https://our.domain.com/rocket
- MONGO_URL=mongodb://mongo:27017/rocketchat
- MONGO_OPLOG_URL=mongodb://mongo:27017/local
- Accounts_UseDNSDomainCheck=false
depends_on:
- mongo
ports:
- 3000:3000
mongo:
image: mongo
restart: unless-stopped
volumes:
- ./data/runtime/db:/data/db
- ./data/dump:/dump
command: mongod --smallfiles --replSet rs0
labels:
- "traefik.enable=false"
Relevant logs:
docker logs show this:
(node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 4): Error: url must be a relative URL:
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 with the NGINX location /rocket proxy_pass and the Docker ROOT_URL configuration, then reproduce the 504 while checking the reported “url must be a relative URL” log entry. Done means web applications respond correctly through the /rocket subdirectory without duplicated routing or gateway timeouts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, nginx
- Domain
- backend, devops, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100