# Ubuntu manual installation guide wrong

**URL:** <https://forums.rocket.chat/t/ubuntu-manual-installation-guide-wrong/9634>\
**Category:** Community Support\
**Created:** [December 8, 2020, 7:00pm UTC](https://forums.rocket.chat/t/ubuntu-manual-installation-guide-wrong/9634 "2020-12-08T19:00:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Roy.Hess](https://avatars.discourse-cdn.com/v4/letter/r/a5b964/32.png) [@Roy.Hess](https://forums.rocket.chat/u/Roy.Hess)\
**Post date:** [December 8, 2020, 7:00pm UTC](https://forums.rocket.chat/t/ubuntu-manual-installation-guide-wrong/9634/1 "2020-12-08T19:00:24Z")

</div>

precisely Following the manual installation of Rocket.Chat for Ubuntu 18.04LTS just throws me errors in journalctl about node things… fuse… fuse/future and whatnot.

I just would like to know why nobody has yet complained about the manual installation guide being outdated/wrong.  
Why can’t Rocket.Chat just work out of the box, why is it so insanely complicated and has so many dependencies for specific versions of specific packages?

### Server Setup Information

- Version of Rocket.Chat Server: latest
- Operating System: Ubuntu 18.04LTS
- Deployment Method: manual install
- Number of Running Instances: 1
- DB Replicaset Oplog: 01
- NodeJS Version: latest
- MongoDB Version: latest
- Proxy: nginx
- Firewalls involved: -

---

<div class="post-metadata">

**Author:** ![Roy.Hess](https://avatars.discourse-cdn.com/v4/letter/r/a5b964/32.png) [@Roy.Hess](https://forums.rocket.chat/u/Roy.Hess)\
**Post date:** [December 8, 2020, 7:02pm UTC](https://forums.rocket.chat/t/ubuntu-manual-installation-guide-wrong/9634/2 "2020-12-08T19:02:55Z")

</div>

I have a manual installation of Rocket.Chat running on another server (ubuntu 2004, rocketchat 3.7.1, node 12.14.0, mongo 4.0.21, npm 6.13.4) and I dare not updating this one.  
I bet every even slightest smallest update will break everything and Rocket.Chat will refuse to work again.

---

<div class="post-metadata">

**Author:** ![fdellwing](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/fdellwing/32/1737_2.png) [@fdellwing](https://forums.rocket.chat/u/fdellwing)\
**Post date:** [December 15, 2020, 1:25pm UTC](https://forums.rocket.chat/t/ubuntu-manual-installation-guide-wrong/9634/3 "2020-12-15T13:25:21Z")

</div>

Just use docker, this is a 3 node cluster. Can simply be changed to 1 node if you want to. Running node applications directly on the OS is asking for trouble.

```auto
version: '2'

services:
  rocketchat:
    image: rocketchat/rocket.chat:latest
    command: >
      bash -c
        "for i in `seq 1 30`; do
          node main.js &&
          s=$$? && break || s=$$?;
          echo \"Tried $$i times. Waiting 5 secs...\";
          sleep 5;
        done; (exit $$s)"
    restart: unless-stopped
    volumes:
      - ./uploads:/app/uploads
    environment:
      - PORT=3000
      - ROOT_URL=http://chat.example.com
      - MONGO_URL=mongodb://rocket:supersecretpassword@rocket-1:27017,rocket-2:27017,rocket-3:27017/rocketchat?authSource=admin&replicaSet=rs0&readPreference=primaryPreferred&w=majority
      - MONGO_OPLOG_URL=mongodb://oploguser:supersecretpassword@rocket-1:27017,rocket-2:27017,rocket-3:27017/local?authSource=admin&replicaSet=rs0
      - INSTANCE_IP=172.16.0.2
# - MAIL_URL=smtp://smtp.email
# - HTTP_PROXY=http://proxy.domain.com
# - HTTPS_PROXY=http://proxy.domain.com
    depends_on:
      - mongo
    ports:
      - 172.16.0.2:3000:3000
    extra_hosts:
        - "rocket-1:172.16.0.2"
        - "rocket-2:172.16.0.3"
        - "rocket-3:172.16.0.4"
        - "rocket-proxy:172.16.0.5"

  mongo:
    image: mongo:3.6.9
    restart: unless-stopped
    volumes:
     - /root/mongo/arb:/data/db
     - /root/mongo:/opt/keyfile
    command: mongod --smallfiles --keyFile /opt/keyfile/mongodb-keyfile --replSet rs0 --storageEngine=wiredTiger
    ports:
      - 172.16.0.2:27017:27017
    extra_hosts:
        - "rocket-1:172.16.0.2"
        - "rocket-2:172.16.0.3"
        - "rocket-3:172.16.0.4"
        - "rocket-proxy:172.16.0.5"
```