If you have questions about snaps best place to ask them is at the #ubuntu-snap channel.
Snaps are one of our biggest install base. They are also auto updating. As a result we like to spend more time testing before releasing. Updated Snaps are usually released around the 15th of the month - around 2 weeks after a new release. This gives us time to look for issues so you don't have to.
If you have special requirements and really need to use the latest release immediately then please consider another installation method e.g docker
You can change the default port (port 3000) to something else by changing the port
configuration option. For example, if you wanted to change the HTTP port to 8080 instead of 3000:
sudo snap set rocketchat-server port=8080
Make sure you restart the rocketchat-service
service afterward for the change to take effect. Read here for more information on that. Your only need to restart the Rocket.Chat application itself, not the database or Caddy.
For enabling TLS/SSL, check out our guide for enabling caddy here.
Make sure you're using x64 or amd64 (or armhf) images, especially on VPS or VMs. x86 (32-bit) is not supported.
While updates happen automatically usually within 6 hours from the time of release, you can update manually by issuing this command:
sudo snap refresh rocketchat-server
sudo snap revert rocketchat-server
The Rocket.Chat snap provides three services. Outside of the snap context, globally, each service is named like snap.<SnapName>.<SnapServiceName>
. Look at the table down below to have a better understanding.
Service | Snap Service Name | Systemd Service Name |
---|---|---|
MongoDB | rocketchat-mongo | snap.rocketchat-server.rocketchat-mongo |
Caddy | rocketchat-caddy | snap.rocketchat-server.rocketchat-caddy |
Rocket.Chat | rocketchat-server | snap.rocketchat-server.rocketchat-server |
You can check the list of services yourself with:
snap info rocketchat-server
Look for the services
section.
You can check whether either or all of them are running or not with the following command:
snap services rocketchat-server
Look into the third column (Current
) that logs the current state of the services.
Another option is to use the systemctl
command. To quickly check if a service is active or not, use the is-active
subcommand or the more well-known status
subcommand. See the above table to know the name of the service you want to inspect.
systemctl is-active snap.rocketchat-server.rocketchat-mongo
systemctl is-active snap.rocketchat-server.rocketchat-caddy
systemctl is-active snap.rocketchat-server.rocketchat-server
Or use the status
subcommand:
systemctl status snap.rocketchat-server.rocketchat-mongo
systemctl status snap.rocketchat-server.rocketchat-caddy
systemctl status snap.rocketchat-server.rocketchat-server
You can either use the snap logs
command, or the systemd alternative, journalctl
. Always refer to this table to know which service name to use where.
Using snap logs
:
sudo snap logs -f rocketchat-server.rocketchat-server
sudo snap logs -f rocketchat-server.rocketchat-mongo
sudo snap logs -f rocketchat-server.rocketchat-caddy
To see the logs from Rocket.Chat using journalctl
:
sudo journalctl -fu snap.rocketchat-server.rocketchat-server
To see the logs from Mongo or Caddy:
sudo journalctl -fu snap.rocketchat-server.rocketchat-mongo
sudo journalctl -fu snap.rocketchat-server.rocketchat-caddy
If you don't want snaps just updating when available you can set when your snaps will update.
The following example asks the system only to update snaps between 4.00am and 7.00am, and 7.00pm and 10:10pm:
sudo snap set system refresh.timer=4:00-7:00,19:00-22:10
You can find more about your options in the snapcraft documentation.
This follows the similar structure as many of the previous questions. You can use both the snap
command or systemctl
to restart RocketChat.
With snap
you get the added benefit of restarting all of the services with a single command:
sudo snap restart rocketchat-server
You can also restart each service individually:
sudo snap restart rocketchat-server.rocketchat-server
sudo snap restart rocketchat-server.rocketchat-mongo
sudo snap restart rocketchat-server.rocketchat-caddy
To restart Rocket.Chat using systemctl
:
sudo systemctl restart snap.rocketchat-server.rocketchat-server
Mongo and Caddy can similarly be restarted:
sudo systemctl restart snap.rocketchat-server.rocketchat-mongo
sudo systemctl restart snap.rocketchat-server.rocketchat-caddy
The snap's policy is to restart on failure.
sudo snap stop rocketchat-server.rocketchat-server
Please note: while the rocketchat-server service should be stopped, the rocketchat-mongo service should be kept running!
systemctl is-active snap.rocketchat-server.rocketchat-mongo
You should get active
as a response.
sudo snap run rocketchat-server.backupdb
If all goes well, you will see some output similar to:
[+] A backup of your data can be found at /var/snap/rocketchat-server/common/backup/rocketchat_backup_<timestamp>.tar.gz
sudo snap start rocketchat-server.rocketchat-server
sudo snap stop rocketchat-server.rocketchat-server
Please note: while the rocketchat-server service should be stopped, the rocketchat-mongo service should be kept running!
systemctl is-active snap.rocketchat-server.rocketchat-mongo
You should get active
as a response.
sudo cp rocketchat_backup.tar.gz /var/snap/rocketchat-server/common/
sudo snap run rocketchat-server.restoredb /var/snap/rocketchat-server/common/rocketchat_backup.tgz
*** ATTENTION ***
* Your current database WILL BE DROPPED prior to the restore!
* Do you want to continue?
1) Yes
2) No
#?
Select 1 or 2 according to your need.
[*] Extracting backup file...
[*] Restoring data...
[*] Preparing database...
[+] Restore completed! Please restart the snap.rocketchat services to verify.
If something goes wrong, you will instead be presented with a path to the relevant log file to help remedy errors. In this case, the database may not be usable until a restore is successfully performed.
sudo snap start rocketchat-server.rocketchat-server
You might want to access the mongo shell shipped with our Rocket.Chat snap. To do so, run:
rocketchat-server.mongo
You can find the mongod configuration file in /var/snap/rocketchat-server/current/mongod.conf
.
Note that the interface providing the ability to access removable media is not automatically connected upon installation, so if you'd like to use external storage (or otherwise use a device in /media
for data), you need to give the snap permission to access removable media by connecting that interface:
sudo snap connect rocketchat-server:removable-media
- Your actual snap files for each version of Rocket.Chat are copied to:
/var/lib/snapd/snaps
and they are mounted in read-only mode. - Your snap common directory is:
/var/snap/rocketchat-server/common/
; file uploads to disk and the database are stored here. - Your snap data directory is
/var/snap/rocketchat-server/<version>
; this is a versioned folder. - You can access the current snap data directory at
/var/snap/rocketchat-server/current
.
You can do this by issuing the following command, where N
is the desired version:
snap remove --revision=N rocketchat-server
snapcraft prime
snap try prime --devmode
cp /usr/bin/strace prime
snap run <snap.app> --shell
sudo ./strace
Starting from release 0.73, it is possible to configure these environmental variables through snap hooks like this:
sudo snap set rocketchat-server port=<another-port>
sudo snap set rocketchat-server mongo-url=mongodb://<your-url>:<your-port>/<your-db-name>
sudo snap set rocketchat-server mongo-oplog-url=mongodb://<your-url>:<your-port>/local
Remember to restart rocket.chat service after setting new values:
sudo systemctl restart snap.rocketchat-server.rocketchat-server.service
This is an example to run rocket.chat on port 4000 instead of 3000 and set database name to rocketchat instead of parties:
sudo snap set rocketchat-server port=4000
sudo snap set rocketchat-server mongo-url=mongodb://localhost:27017/rocketchat
sudo systemctl restart snap.rocketchat-server.rocketchat-server.service
Starting from release 0.73, it is possible to overwrite any Rocket.Chat environmental variables dropping files ending in .env
in $SNAP_COMMON directory (/var/snap/rocketchat-server/common/
), for example, you can create a file to change SMTP settings:
cat /var/snap/rocketchat-server/common/overwrite-smtp.env
OVERWRITE_SETTING_SMTP_Host=my.smtp.server.com
Remember to restart rocket.chat service after creating .env files:
sudo systemctl restart snap.rocketchat-server.rocketchat-server.service
More than one .env file is allowed, and more than one environmental variable defined per file is allowed.
To set a registration token for your server, create any file ending in .env
under /var/snap/rocketchat-server/current/
with content:
REG_TOKEN=<your token>
Then restart your server
sudo systemctl restart snap.rocketchat-server.rocketchat-server