In most situations, the configuration options shown in the example config in snikket-selfhosted should suffice. In some cases of more complex requirements (such as running behind a reverse proxy), it may be required to tweak more options. They are described here.
Configuration Option Reference
This reference is in no particular order. Most importantly, it is certainly not in the order of “things you should try to mess with come first”.
The domain name of your Snikket instance. Do not change this after it was once set.
The number of days (as integer) for which your server should preserve messages so that all devices of a user can catch up, even if they end up being disconnected from the internet for a while.
The Snikket Server stores all messages which are sent to any user for the given number of days. As end-to-end encryption is used, no plaintext is generally stored, only encrypted messages. These messages are then decrypted only on the devices of the specific user.
It is recommended to set this number not too small. If a device is offline for longer than the number of days this option is set to, it will not receive all messages, which is generally a bad user experience. Note that it does no matter if any other device has received the messages: If a user has only a single device and is offline for more days than the retention period is set to, they will lose messages.
On the other hand, storing too many messages on the server causes impacts on server performance and data hygiene in general. The default of seven is considered reasonable in the sense that most users won’t be offline for longer than that.
Changing this option to a lower value will delete messages from the server. Changing this option to a higher value will allow messages existing on the server to be retained for longer.
Use this option to place a limit on the amount of storage Snikket will use for files shared by users. You can use this to prevent your server’s disk capacity being consumed if users upload many large files. By default there is no limit.
If the limit is reached, users will be unable to upload new files until older files are cleared by Snikket after the configured retention period (or the limit is increased).
# Allow no more than 1.5GB disk space to be used by uploaded files SNIKKET_UPLOAD_STORAGE_GB=1.5
The amount of file storage used is affected by the configured retention period (7 days by default) - i.e. longer retention periods will mean files are stored for longer, and more space will be used. Take this into account when choosing a value.
Control the detail level of the log output of the snikket server.
Valid options are
info (the default) and
debug log level is very detailed. It may quickly fill your disk and also contain more sensitive information.
A human-friendly name for your server. Defaults to the value of
By default, Snikket sends anonymous requests for the latest release via DNS, to provide you with a notification when a new release is available (which may contain important security fixes). This behaviour can be disabled by setting the option to
This will not expose your server’s IP address or domain name to the Snikket org, as it will generally be proxied through your or your hosters Internet Service Provider’s DNS servers.
Email address of the admin. This will be sent to all new users as contact information.
The time (in seconds) for which the web portal will allow avatars to be cached by browsers.
Arcane Configuration Reference
The options below this line are even more arcane than the options above. Do not touch unless you truly know what you’re doing.
The TCP port on which the internal HTTP API listens on. The default is
5280. Do not change this without also changing
The IP address on which the internal HTTP API listens on. The default is
127.0.0.1, so that the API is only accessible from the same server. Changing this may be a security risk as some general system information is accessible without authentication.
The URL template for invitation links. The server needs to know under which address the invitation service is hosted.
Changing this will most likely break your invitation flow, so better don’t.
Just do not set this.
Also better do not set this.
Enable IPv6 support.
By default, IPv6 is disabled because most container runtimes default to it being disabled. Enabling IPv6 in the server could cause issues if the container runtime does not support it.
If you are monitoring your Snikket server using Prometheus and scraping the metrics endpoint, you should set this to
1 and let it at its default otherwise.
If this is set to
1 without Snikket server being scraped by Prometheus, the System Health panel in the web portal will not work correctly. If this is not set to
1 when Snikket is being scraped by Prometheus, the numbers seen by Prometheus may not be accurate at the time they are being sampled, as Snikket server will in that case sample data only every 60s, no matter how often or when you scrape.
The default is safe for non-Prometheus setups.
By default, Snikket starts a STUN/TURN server. If this option is set to
0, it will not do that. You will have to run your own STUN/TURN server and configure
SNIKKET_TWEAK_TURNSERVER is set to
SNIKKET_TWEAK_TURNSERVER_DOMAIN is not set, no STUN/TURN server will be offered to your users. Terrible idea to do that, will break audio/video calls in all but the most ideal situations.
Hostname of the STUN/TURN server to use.
Defaults to the Snikket domain, as snikket-server runs contains its own STUN/TURN server.
Shared secret to use with the STUN/TURN server for authentication of clients.
Defaults to a secret which is generated once at first installation. Only override this if you also set
0 and set
SNIKKET_TWEAK_TURNSERVER_DOMAIN to a STUN/TURN server you operate manually.
Expose the file share service at the
SNIKKET_DOMAIN instead of at
This nowadays conflicts with the web portal, so you should not set it.
Path or glob for extra configuration files to load.