I have a Mattermost instance running on a gitlab server. I’m using the gitlab server for SSO. Both Gitlab and Mattermost are using HTTPS, with an SSL cert for an authority. The system worked fine until the last Gitlab update. Now Mattermost works for a few min after booting the system, then fails with “Error Unable to save the token.” In the logs it appears Mattermost can no longer contact the Gitlab server. They are running on the same machine. I turned off the IDS, IPS, and UFW to try to troubleshoot this. But it still seems to fail. Anybody have any idea of what I could take a look at next?
Related Topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Unable to save token - MM + Gitlab SSO | 6 | 2822 | June 11, 2020 | |
| "Token request failed" error on GitLab Mattermost | 7 | 5868 | April 5, 2020 | |
| Error retrieving the token | 5 | 3504 | September 23, 2020 | |
| Connection reset on Gitlab Mattermost + Gitlab SSO | 3 | 1900 | August 18, 2017 | |
| Configure stand-alone mattermost with gitlab sign-on | 16 | 7278 | August 29, 2019 |