18.2.x: Links on self hosted gitlab instances project list are missing relative url part / context path since 18.2.0 (from gitlab)

[th-2021]

gitlab#556264

[sachilles]

@th-2021 This doesn't sound good.

[th-2021]

This won't be fixed before 18.3.0 (maybe even later).

[sachilles]

Unfortunately, in addition I realised a bug by creating user defined tokens.

[kkimurak]

I'm not sure about user defined tokens issue, but the issue about link in project list seems to be fixed and backported to 18.2.2. Confirmed on my test env and then main env.
Some users have reported getting an error about the relative_url_root configuration parameter not being supported ( gitlab.com/gitlab-org/gitlab#556264 (comment) ), but I believe this is an issue with omnibus installations (and official docker images based on omnibus installations). This did not happen in my environment, and the error message included a path specific to omnibus installations (/opt/gitlab).

[sachilles]

I can confirm that this problem exists. Following https://forum.gitlab.com/t/created-personal-access-tokens-not-listed-and-not-usable/128318/7 I have the feeling, that this problems is related to reverse-proxies (in my case the reverse-proxy terminates the https connection and the communication between the proxy and the docker container is just an http conection).

Using the browser built-in developer tools I relized that the users subpage for personal access tokens uses an API call (GET
http://<FQDN_OF_SERVER>/api/v4/personal_access_tokens?user_id=<user_id>&sort=expires_asc&page=1&state=active) that is blocked. Currently I have no idea why this happens.

[sachilles]

@kkimurak I tracked the problem a bit and it turned out, that the headers related to the content security ppolicy in combination with the nginx of our image (used without SSL) and an (external) SSL termination proxy blocks the script for showing and generating personal acess tokens. (Currently, in my case are three tokens present.)

[sachilles]

@kkimurak Hi, using the correct configuration for our GitLab image (and checking it's documentation) might be helpful. In my case, I did not set the GITLAB_HTTPS option to true. Setting this option solved the CSP issues.