diff options
Diffstat (limited to 'doc/install')
| -rw-r--r-- | doc/install/Production-Ubuntu.md | 2 | ||||
| -rw-r--r-- | doc/install/Requirements.md | 2 | ||||
| -rw-r--r-- | doc/install/Troubleshooting.md | 6 |
3 files changed, 8 insertions, 2 deletions
diff --git a/doc/install/Production-Ubuntu.md b/doc/install/Production-Ubuntu.md index 97d846a4a..098707ada 100644 --- a/doc/install/Production-Ubuntu.md +++ b/doc/install/Production-Ubuntu.md @@ -42,7 +42,7 @@ 1. Unzip the Mattermost Server by typing: * ``` tar -xvzf mattermost.tar.gz``` 1. For the sake of making this guide simple we located the files at `/home/ubuntu/mattermost`. In the future we will give guidance for storing under `/opt`. -1. We have also elected to run the Mattermost Server as the `ubuntu` account for simplicity. We recommend settings up and running the service under a `mattermost` user account with limited permissions. +1. We have also elected to run the Mattermost Server as the `ubuntu` account for simplicity. We recommend setting up and running the service under a `mattermost` user account with limited permissions. 1. Create the storage directory for files. We assume you will have attached a large drive for storage of images and files. For this setup we will assume the directory is located at `/mattermost/data`. * Create the directory by typing: * ``` sudo mkdir -p /mattermost/data``` diff --git a/doc/install/Requirements.md b/doc/install/Requirements.md index 61fa8e7be..b877b6dc0 100644 --- a/doc/install/Requirements.md +++ b/doc/install/Requirements.md @@ -47,7 +47,7 @@ The Mattermost roadmap does not currently include production support for Fedora, Mattermost offers both real-time communication and file sharing. CPU and Memory requirements are typically driven by the number of concurrent users using real-time messaging. Storage requirements are typically driven by number and size of files shared. -The below guidelines offer estimates based on real world usage of Mattermost across industries. +The below guidelines offer estimates based on real world usage of Mattermost in multi-team configurations ranging from 10-100 users per team. ### CPU diff --git a/doc/install/Troubleshooting.md b/doc/install/Troubleshooting.md index 7166f9978..51699a39c 100644 --- a/doc/install/Troubleshooting.md +++ b/doc/install/Troubleshooting.md @@ -28,3 +28,9 @@ The following is a list of common error messages and solutions: ###### `panic: runtime error: invalid memory address or nil pointer dereference` - This error can occur if you have manually manipulated the Mattermost database, typically with deletions. Mattermost is designed to serve as a searchable archive, and manual manipulation of the database elements compromises integrity and may prevent upgrade. - **Solution:** Restore from database backup created prior to manual database updates, or reinstall the system. + +###### `Token request failed` + - This error can appear in the web browser after attempting to create a new team with GitLab SSO enabled + - **Solutions:** + 1. Check that your SSL settings for the SSO provider match the `http://` or `https://` choice selected in `config.json` under `GitLabSettings` + 2. Follow steps 1 to 3 of the manual [GitLab SSO configuration procedure](https://github.com/mattermost/platform/blob/master/doc/integrations/Single-Sign-On/Gitlab.md) to confirm your `Secret` and `Id` settings in `config.json` match your GitLab settings, and if they don't, manually update `config.json` to the correct settings and see if this clears the issue. |