timeout on first install

Open
  • Is something wrong?
#148 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
docker, nodejs
Domain
devops, infrastructure

Research direction

Start with the official Docker setup and inspect the Rocket.Chat and nginx logs for the registration request. Compare the upstream timeout with the Rocket.Chat SMTP ETIMEDOUT output and the container status. Done means the initial admin account can be created without the request hanging and the containers remain healthy.

Written by the indexing model from the issue text.

Description

Hello I am following this official setup https://docs.rocket.chat/installing-and-updating/docker-containers
everything seems ok until I try to go to the url and create an admin account, it will just hang forever and on the nginx logs it says it timedout...

 tail -f rocketchat_error.log 
2021/07/19 16:55:58 [error] 7329#7329: *1 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 213.xx.xx.xx, server: chat.xxxxxx.com, request: "POST /api/v1/method.callAnon/registerUser HTTP/1.1", upstream: "http://127.0.0.1:3000/api/v1/method.callAnon/registerUser", host: "chat.xxxxxx.com", referrer: "https://chat.xxxxxxx.com/setup-wizard/1"

docker ps

docker ps
CONTAINER ID   IMAGE                                                COMMAND                  CREATED         STATUS                          PORTS                                       NAMES
8682114feb1b   rocketchat/hubot-rocketchat:latest                   "/bin/sh -c 'node -e…"   7 minutes ago   Restarting (1) 57 seconds ago                                               opt_hubot_1
368c7ea41010   registry.rocket.chat/rocketchat/rocket.chat:latest   "docker-entrypoint.s…"   7 minutes ago   Up 7 minutes                    0.0.0.0:3000->3000/tcp, :::3000->3000/tcp   opt_rocketchat_1
91b31e9d5b63   mongo:4.0                                            "docker-entrypoint.s…"   7 minutes ago   Up 7 minutes                    27017/tcp                                   opt_mongo_1

on a netstat I do not see mongo port listening on 127.0.0.1 ..... could this be the issue?
I have not change anything only where I am supposed to add my domain on the docker compose yaml file.

[edit]

docker ps --format "{{.Ports}}"

0.0.0.0:3000->3000/tcp, :::3000->3000/tcp
27017/tcp

[edit 2]

rocketchat_1          | ➔ +----------------------------------------------------+
rocketchat_1          | Error: Connection timeout
rocketchat_1          |     at SMTPConnection._formatError (/app/bundle/programs/server/npm/node_modules/meteor/email/node_modules/nodemailer/lib/smtp-connection/index.js:784:19)
rocketchat_1          |     at SMTPConnection._onError (/app/bundle/programs/server/npm/node_modules/meteor/email/node_modules/nodemailer/lib/smtp-connection/index.js:770:20)
rocketchat_1          |     at Timeout.<anonymous> (/app/bundle/programs/server/npm/node_modules/meteor/email/node_modules/nodemailer/lib/smtp-connection/index.js:235:22)
rocketchat_1          |     at listOnTimeout (internal/timers.js:554:17)
rocketchat_1          |     at processTimers (internal/timers.js:497:7) {
rocketchat_1          |   code: 'ETIMEDOUT',
rocketchat_1          |   command: 'CONN'
rocketchat_1          | }
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.