Skip to content

Latest commit

 

History

History
37 lines (21 loc) · 1.83 KB

common-deploy-faq.rst

File metadata and controls

37 lines (21 loc) · 1.83 KB
orphan:
nosearch:

Why doesn't Mattermost start at system boot?

To have the Mattermost Server start at system boot, the systemd unit file needs to be enabled. Run the following command:

sudo systemctl enable mattermost.service

Why does Mattermost fail to start at system boot?

If your database is on the same system as your Mattermost Server, we recommend editing the default /lib/systemd/system/mattermost.service systemd unit file to add After=postgresql.service and BindsTo=postgresql.service to the [Unit] section.

Can I run Mattermost without a proxy?

Yes. Mattermost binds to 443 instead of 8065. The Mattermost binary requires the correct permissions to do that binding. You must activate the CAP_NET_BIND_SERVICE capability to allow the new Mattermost binary to bind to ports lower than 1024 by running the following command:

sudo setcap cap_net_bind_service=+ep ./mattermost/bin/mattermost

Note

We highly recommend using a proxy in front of Mattermost server for up to 200 concurrent users. If you have fewer than 200 concurrent users, you can :doc:`set up TLS </install/setup-tls>`. If you're exceeding 200 concurrent users, you'll need :doc:`a proxy </install/setup-nginx-proxy>`, such as NGINX, in front of Mattermost to manage the traffic.

Where can I access Mattermost Server logs?

Mattermost Server logs are located in the logs directory of wherever you installed Mattermost. By default, this is /opt/mattermost/logs, inside the mattermost.log file.