mirror of
https://github.com/mattermost/mattermost.git
synced 2025-02-25 18:55:24 -06:00
Adding "Solution" sections to guide
This commit is contained in:
@@ -17,11 +17,14 @@
|
||||
The following is a list of common error messages and solutions:
|
||||
|
||||
###### `Please check connection, Mattermost unreachable. If issue persists, ask administrator to check WebSocket port.`
|
||||
- Message appears in blue bar on team site. Check that [your websocket port is properly configured](https://github.com/mattermost/platform/blob/master/doc/install/Production-Ubuntu.md#set-up-nginx-server).
|
||||
- Message appears in blue bar on team site.
|
||||
- **Solution:** Check that [your websocket port is properly configured](https://github.com/mattermost/platform/blob/master/doc/install/Production-Ubuntu.md#set-up-nginx-server).
|
||||
|
||||
|
||||
###### `x509: certificate signed by unknown authority` in server logs when attempting to sign-up
|
||||
- This error may appear when attempt to use a self-signed certificate to setup SSL, which is not yet supported by Mattermost. You can resolve this issue by setting up a load balancer like Ngnix. A ticket exists to [add support for self-signed certificates in future](x509: certificate signed by unknown authority).
|
||||
- This error may appear when attempt to use a self-signed certificate to setup SSL, which is not yet supported by Mattermost. You
|
||||
- **Solution:** Set up a load balancer like Ngnix [per production install guide](https://github.com/mattermost/platform/blob/master/doc/install/Production-Ubuntu.md#set-up-nginx-with-ssl-recommended). A ticket exists to [add support for self-signed certificates in future](x509: certificate signed by unknown authority).
|
||||
|
||||
###### `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 databse backup created prior to manual database updates, or reinstall the system.
|
||||
|
||||
Reference in New Issue
Block a user