Loading animation and attempt to POST to localhost:3000

Open
#199 7 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
docker

Research direction

Start with the untouched compose.yaml and the .env values, especially ROOT_URL, then reproduce the browser request to /meteor/dynamic-import/fetch through the HAProxy SSL-offload setup. Done means the deployed Rocket.Chat instance loads without attempting to POST to localhost:3000.

Written by the indexing model from the issue text.

Description

Hi all,
I'm running Haproxy (ssl offload) ->rocketchat(docker).
The container starts ok but in the browser i can only see the three dots animation and in my browser dev-tools/network i see a failed POST request to localhost:3000.

The request is:

http://localhost:3000/__meteor__/dynamic-import/fetch

I would expect that the configuration of the url is picked up from .env ROOT_URL
It seems to me that something keeps using localhost:3000 for URL building.
Do you guys know what this can be?

Here is my env, the compose.yaml is untouched:

### Rocket.Chat configuration

# Rocket.Chat version
# see:- https://github.com/RocketChat/Rocket.Chat/releases
#RELEASE=
# MongoDB endpoint (include ?replicaSet= parameter)
#MONGO_URL=
# MongoDB endpoint to the local database
#MONGO_OPLOG_URL=
# IP to bind the process to
#BIND_IP=
# URL used to access your Rocket.Chat instance
ROOT_URL=https://rchat.example.com
# Port Rocket.Chat runs on (in-container)
#PORT=
# Port on the host to bind to
#HOST_PORT=

### MongoDB configuration
# MongoDB version/image tag
#MONGODB_VERSION=
# See:- https://hub.docker.com/r/bitnami/mongodb

### Traefik config (if enabled)
# Traefik version/image tag
#TRAEFIK_RELEASE=
# Domain for https (change ROOT_URL & BIND_IP accordingly)
DOMAIN=rchat.example.com
# Email for certificate notifications
#LETSENCRYPT_EMAIL=

Do I need to disable traefik in compose.yaml?

Many thanks in advance.

Dominant language
Dockerfile
Stars
336
Forks
226
Avg merge
21d 4h
Merged PRs (30d)
1

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from RocketChat/Docker.Official.Image

All issues in RocketChat/Docker.Official.Image

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.