Cannot integrate with self-hosted GitLab installed at relative URL (domain/path)

[yusufali94]

Bug description

Environment: gitpod.io and my self hosted gitpod instance
Gitlab Instance: http://<domain>/gitlab
(See https://docs.gitlab.com/ee/install/relative_url.html)

Note:
Able to successfully authorize gitlab as an integration. On my self hosted, was able to authorize as a oauth provider and login using the self hosted gitlab. Enabled GitPod at user level and at the gitlab instance level.

Steps to reproduce

1. Go to repository. Url of repo is: https:///gitlab/drgroot/gitpod
   

2. Use bookmark to attach to gitpod.io
   https://gitpod.io/#https://<domain>/gitlab/drgroot/gitpod
   

3. Try using gitpod button
   https://gitpod.io/#https://<domain>/gitlab/drgroot/-/tree/master
   Asks for permissions:
   

Click request, and it takes be back to https://gitpod.io/#https://<domain>/gitlab/drgroot/-/tree/master
Now I get

4. Try using this url
   https://gitpod.io/#https://<domain>/gitlab/drgroot/tree/master
   Same as 3, except final error is:
   

Anything else?

tried the same steps on my selfhosted gitpod, updating the gitpod url on my gitlab instance to my selfhosted URL, noticed this in the logs:

Selfhosted version: 0.10.0
Kuberntes Type: k3s

Note: all github repos public and private work perfectly....

[yusufali94]

update, I also saw this in the logs:

UPDATE: it is because the gitlab instance is "domain.com/gitlab". I re-installed gitlab to "gitlab.domain.com" and it worked. The last log about additional context gave the hint.

[ghuntley]

ah @yusufali94 how were you doing domain.com/gitlab? Were you reverse proxying GitLab using nginx?

[yusufali94]

yes and it did not work. but when I re-installed gitlab to use a full subdomain behind the nginx proxy, it worked fine. The issue was not the proxy. I tried removing my proxy and it made no difference. It only worked when my gitlab instance was subdomain without a path designation.