Rocketchat setup wizard won’t get past page 1 Docker setup on Ubuntu 18.04

zedred79 commented 4 years ago

Description:

I used the official docker-compose script and only changed the ROOT_URL variable. I tried on my Ubuntu 18.04 server and on google cloud Ubuntu 20.04 virtual machine. When I load the setup wizard page, I insert the data and press the continue button but the page freezes. If I try to reload the page the normal login page appears, but obviously there is no user to log in.

Steps to reproduce:

Copy https://github.com/RocketChat/Rocket.Chat/blob/develop/docker-compose.yml
Chage the ROOT_URL with my url
sudo docker-compose up -d mongo
sudo docker-compose up -d mongo-init-replica
sudo docker-compose up -d rocketchat
From browser loard page http://myurl:3000
Setup wizard page 1 is loaded
Fill in the data and press continue

Expected behavior:

It should go to setup page 2

Actual behavior:

The page is frozen and nothing happens

Server Setup Information:

Version of Rocket.Chat Server: 3.5.4
Operating System: Ubuntu Server 18.04
Deployment Method: docker-compose
Number of Running Instances: 1
DB Replicaset Oplog: Enabled
NodeJS Version: 12.16.1 - x64
MongoDB Version: 4.0.20

Client Setup Information

Chrome 85.0.4183.83, Edge 85.0.564.41, Firefox 80.0
Windows

Additional context

Relevant logs:

LocalStore: store created at
LocalStore: store created at
LocalStore: store created at
Setting default file store to GridFS
ufs: temp directory created at “/tmp/ufs”
Loaded the Apps Framework and loaded a total of 0 Apps!
Using GridFS for custom sounds storage
Using GridFS for custom emoji storage
Updating process.env.MAIL_URL
Browserslist: caniuse-lite is outdated. Please run next command npm update
(node:8) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use th
e Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
➔ System ➔ startup
➔ ±--------------------------------------------------+
➔ | SERVER RUNNING |
➔ ±--------------------------------------------------+
➔ | |
➔ | Rocket.Chat Version: 3.5.4 |
➔ | NodeJS Version: 12.16.1 - x64 |
➔ | MongoDB Version: 4.0.20 |
➔ | MongoDB Engine: mmapv1 |
➔ | Platform: linux |
➔ | Process Port: 3000 |
➔ | Site URL: http://X.X.X.X:3000 |
➔ | ReplicaSet OpLog: Enabled |
➔ | Commit Hash: ef234790be |
➔ | Commit Branch: HEAD |
➔ | |

murtaza98 commented 4 years ago

Hi, I too was facing this issue. The workaround I found works like this,

When u first load the server, n go to the setup page no 1, there enter the email and password and other details
Close this page if it gets stuck.
Go again to the server URL, preferably from an incognito window. Now, this should give u a login screen. Here enter the email and password u added in step 1.
If step 3 works, it should redirect u to setup page 2 where u can continue you setup

zedred79 commented 4 years ago

You saved me. When I go back to the home page, if I enter my username and password, it reports an error, but if I enter my email and password, I can proceed. Now everything works.

RaelZero commented 4 years ago

Faced the same issue on two different setups (though it shouldn't matter too much AFAIK):

Ubuntu Server 16.04.7 LTS (Docker version 18.09.7, build 2d0083d; docker-compose version 1.24.0, build 0aa59064)
Arch Linux updated to today (Docker version 19.03.12-ce, build 48a66213fe; docker-compose version 1.26.2, build unknown).

Eventually resolved by doing the following:

delete all stored data on my filesystem
add definitions for ADMIN_USERNAME, ADMIN_EMAIL and ADMIN_PASS in the docker-compose.yml file (services -> rocketchat -> environment)
re-launch the Compose stack (docker-compose up -d)
log in with details provided in the Compose file
continue setup normally

Edit: Tried giving a cursory look at the Rocket.Chat codebase, but I'm really not familiar enough to suggest potential fixes... Sorry!

a-schaefers commented 3 years ago

I too ran in to the same exact issue using docker-compose and near default configuration... @RaelZero has the best workaround.

henris42 commented 3 years ago

I was blocked with the same thing, it should be fixed minimally in the docker compose instructions, it was a total time waster. :(

jschirrmacher commented 2 years ago

I've encountered this problem with Rocket.Chat 4.0.2 when upgrading MongoDB from 4.2 to 4.4. I downgraded after that and found the 4.2 having the same problem. After a few hours trial and error, I found the workaround - which worked for me. Thanks @murtaza98! Would be great if you (at Rocket.Chat) could solve this, because there will be more people stumbling over it and wasting time.

RocketChat / Rocket.Chat