Hello,
GitLab 8.9.4 running fine (Omnibus) in an Ubuntu Server 16.04 virtual machine through port 802:
external_url 'http://gitlab_url:802'
I’ve enabled mattermost by this line in /etc/gitlab/gitlab.rb
:
mattermost_external_url 'http://gitlab_url:8065'
I’ve also opened the port 8065 in my router.
But this is what I get when I try to access that gitlab_url:8065 in a browser:
400 Bad Request
Request Header Or Cookie Too Large
nginx
In the guide, I skipped the “Running GitLab Mattermost on its own server” part because it would be fine for me with the embedded version if I could make it work.
Reading the “Manually (re)authorising GitLab Mattermost with GitLab” part, I went to the Applications
section in the Admin Area
, and I found a “Mattermost” application.
The two urls there were wrong (probably because the first time I set a dummy mattermost_external_url
), so I manually corrected them. I’m not sure if I tried with/without the port or both.
I tried to remove Mattermost Application in GitLab and start again Mattermost configuration. I also tried to reset Mattermost (doing this) but I always get to the same error.
I also tried to set this in /etc/gitlab/gitlab.rb
:
mattermost['gitlab_enable'] = true
mattermost['gitlab_secret'] = "***"
mattermost['gitlab_id'] = "***"
mattermost['gitlab_scope'] = ""
mattermost['gitlab_auth_endpoint'] = "http://gitlab_url:8065/oauth/authorize"
mattermost['gitlab_token_endpoint'] = "http://gitlab_url:8065/oauth/token"
mattermost['gitlab_user_api_endpoint'] = "http://gitlab_url:8065/api/v3/user"
I enabled the log:
mattermost['log_file_directory'] = '/var/log/gitlab/mattermost'
And cat /var/log/gitlab/mattermost/mattermost.log
basically tells me:
!!!Automatic database upgrade failed.!!!
But this is the first time I try to set up Mattermost
Also note everytime I run sudo gitlab-ctl reconfigure
I get a laaarge output
(I posted the same question here)