Error 503 Service Uanavailable (Docker, Reverse Proxy)

Description

I have been running a working instance of Rocket Chat, on my own domain, for a few weeks now. Suddenly this morning I am getting Error 503 Service unavailable when I try to connect to the server on port 3000. The server will still connect on the local machine that is running the docker container (http://192.168.1.XX )but it shows the admin setup page instead of the already configured server.

Server Setup Information

  • Version of Rocket.Chat Server: 3.4.1
  • Operating System: Ubuntu 20
  • Deployment Method: Docker via Docker_compose from rocketchat docs
  • Number of Running Instances: 1
  • DB Replicaset Oplog: enabled
  • NodeJS Version: 12.16.1 x64
  • MongoDB Version: 4.0.19
  • Proxy: Apache reverse proxy SSL engine on
  • Firewalls involved: UFW ports 80, 443 and 3000 open (Problem persists with UFW Disable)

Any additional Information

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
a3839b7b63ec rocketchat/hubot-rocketchat:latest “/bin/sh -c 'node -e…” 39 minutes ago Restarting (1) 46 seconds ago rocketchat_hubot_1
a134e12d24a1 rocketchat/rocket.chat:latest “docker-entrypoint.s…” 39 minutes ago Up 39 minutes 0.0.0.0:80->3000/tcp rocketchat_rocketchat_1
c36094a38134 mongo:4.0 “docker-entrypoint.s…” 7 days ago Up 39 minutes 27017/tcp rocketchat_mongo_1

sudo docker logs -t rocketchat_rocketchat_1
2020-07-13T11:40:11.599275818Z LocalStore: store created at
2020-07-13T11:40:11.674473668Z LocalStore: store created at
2020-07-13T11:40:11.675191941Z LocalStore: store created at
2020-07-13T11:40:12.671592366Z Setting default file store to GridFS
2020-07-13T11:40:22.081440700Z {“line”:“120”,“file”:“migrations.js”,“message”:“Migrations: Not migrating, already at version 197”,“time”:{"$date":1594640422080},“level”:“info”}
2020-07-13T11:40:22.388875942Z ufs: temp directory created at “/tmp/ufs”
2020-07-13T11:40:25.608683034Z Loaded the Apps Framework and loaded a total of 0 Apps!
2020-07-13T11:40:25.836377888Z Using GridFS for custom sounds storage
2020-07-13T11:40:25.845761427Z Using GridFS for custom emoji storage
2020-07-13T11:40:26.111884189Z Browserslist: caniuse-lite is outdated. Please run next command npm update
2020-07-13T11:40:26.202701459Z Updating process.env.MAIL_URL
2020-07-13T11:40:27.266150153Z ➔ System ➔ startup
2020-07-13T11:40:27.267276207Z ➔ ±-------------------------------------------------------+
2020-07-13T11:40:27.267962609Z ➔ | SERVER RUNNING |
2020-07-13T11:40:27.268834985Z ➔ ±-------------------------------------------------------+
2020-07-13T11:40:27.269479652Z ➔ | |
2020-07-13T11:40:27.270145292Z ➔ | Rocket.Chat Version: 3.4.1 |
2020-07-13T11:40:27.270801459Z ➔ | NodeJS Version: 12.16.1 - x64 |
2020-07-13T11:40:27.271490427Z ➔ | MongoDB Version: 4.0.19 |
2020-07-13T11:40:27.272174038Z ➔ | MongoDB Engine: mmapv1 |
2020-07-13T11:40:27.272841001Z ➔ | Platform: linux |
2020-07-13T11:40:27.273475353Z ➔ | Process Port: 3000 |
2020-07-13T11:40:27.274105168Z ➔ | Site URL: https://chat.readcted.net |
2020-07-13T11:40:27.274745900Z ➔ | ReplicaSet OpLog: Enabled |
2020-07-13T11:40:27.275379670Z ➔ | Commit Hash: 21157c0c4f |
2020-07-13T11:40:27.276022127Z ➔ | Commit Branch: HEAD |
2020-07-13T11:40:27.276629671Z ➔ | |
2020-07-13T11:40:27.277105288Z ➔ ±-------------------------------------------------------+

Finally just did my Mongo 4.4 to 5.0 upgrade… but now just getting the 503 error. Container log shows all good with ‘SERVER RUNNING’ status.

Scratch that… I had my ingress pointing to the wrong RC container. Duh!
Anyways, this post worked for me to upgrade M 4.4 to 5.