You may very well be right about this being a problem with serving the Mattermost API at all. On poking this a little more with curl from the server the results don’t seem to be right to me. Of course I’m stabbing it in the dark and don’t know what the expected results are, but it feels like a problem internal to my Mattermost installation.
In particular, I’m sending requests to the 127.0.0.1:8065 address to sidestep any issues introduced by my front end proxy.
-
Requesting
/gives the signup page as expected and a status header of 200. So far so good. The mattermost.log file also gives a normal looking entry (I have it turned up to DEBUG level). -
Requesting
/login/gitlab/completeas entered in the Gitlab application gives back an error page generated by Mattermost and status code of 500. This seems reasonable to me as it probably expects some callback vars and a previous state that doesn’t exist. So far so good. -
Requesting
/teams/create_with_sso/gitlabas mentioned in your post also returns an error page generated by Mattermost, but the status code is 404. Likewise the mattermost.log file has a 404 line:[2015/09/19 06:51:14 UTC] [EROR] /teams/create_with_sso/gitlab: code=404 ip=127.0.0.1
Edit: It looks like the URL called by the page using at XHR request is actually
/api/v1/teams/create_with_sso/gitlab. I tried that as well at it likewise returned 404.
Should that have been a valid URL? What URL’s can I test from CURL to make sure the API is actually firing on all cylinders (as opposed to just being available on the port)?