I’m using a translation tool, so I apologize for any inaccuracies.
Mac (Ventura) - GitLab Docker (16.3.3ee)
Scenario That Worked:
Start GitLab server → Enable Mattermost → Mattermost works as expected.
Scenario That Caused Issues:
While exploring various settings, I removed the Mattermost key from
https://gitlab.myDomain.com/admin/applications → This led to login issues → Resolved the login issue by creating a new application key and adding the following settings to
mattermost_external_url 'https://mattermost.mydomain.com' mattermost_nginx['listen_port'] = 80 mattermost_nginx['listen_https'] = false mattermost['gitlab_enable'] = true mattermost['gitlab_id'] = "myApplicationId" mattermost['gitlab_secret'] = "mySecret" mattermost['gitlab_scope'] = "read_user" mattermost['gitlab_auth_endpoint'] = "http://gitlab.MyDomain.com/oauth/authorize" mattermost['gitlab_token_endpoint'] = "http://gitlab.MyDomain.com/oauth/token" mattermost['gitlab_user_api_endpoint'] = "http://gitlab.MyDomain.com/api/v4/user"
I would like to revert back to the original setup, where Mattermost is enabled without specifying the settings in
gitlab.rb. I’m managing both development and production servers and version-controlling
gitlab.rb with Git. Therefore, having keys hardcoded into the config file is inconvenient for me.
mattermost_external_url 'https://mattermost.mydomain.com' mattermost_nginx['listen_port'] = 80 mattermost_nginx['listen_https'] = false ....other conf erase....
Thank you in advance for your help.