[Bug]: GitLab Authentication always Redirects to gitlab.com

[Blockmaster2706]

Error Message and Logs

It appears that when trying to setup Gitlab as an OAuth Provider, it is impossible to authenticate using a self-hosted Gitlab instance. Clicking "Login with GitLab" always sends you to gitlab.com

Steps to Reproduce

1. Setup OAuth according to https://coolify.io/docs/knowledge-base/oauth
2. Use self-hosted gitlab's domain in Redirect URI field
3. Log out and try to login via GitLab
4. You're sent to gitlab.com instead of your custom domain

Example Repository URL

No response

Coolify Version

v4.0.0-beta.413

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Ubuntu 24.04.2 LTS

Additional Information

No response

[djsisson]

@Blockmaster2706 the coolify oauth is for gitlab.com only not any self hosted version also the redirect uri would need to be for coolify domain in order for the oauth flow to work inside coolify,

[Blockmaster2706]

@djsisson oh, I see. That's quite unfortunate. Maybe this should be specified in the docs or in a hover note, since many people self-host their GitLab instances? But I suppose it would be possible to setup an instance of Authentik to bridge the gap.

[djsisson]

@Blockmaster2706 i will also add, there would be an inherit risk using any of your own self hosted services for oauth, since if the proxy goes down, none of your services are now reachable, meaning you can't use your oauth to log in to coolify

[Blockmaster2706]

@djsisson Right, thanks for the note. However I think this risk would easily be mitigated by having the main admin account for Coolify be available to log into using a standard Email and Password, and only using OAuth for ease of use

[Cinzya]

I will close this issue then, since it's not a bug with the GitLab Authentication itself but you used it incorrectly with a self-hosted GitLab Instance.

If you wish to have support for self-hosted GitLab OAuth integrated, you can open a feature request in the Discussions about it.

If the docs weren't clear enough on that end, we have a dedicated repository for the Coolify Docs here with a seperate team working on it. They don't always read / see discussions about the docs on the coolify repo here, so it's best to open issues related to the docs there.