Configure Google OAuth

Create a Google OAuth client for a web application so Google can return the user's OpenID profile and email address to Coolify.

Example data

Replace the example domain while following this guide:

  • Coolify URL: https://coolify.shadowarcanist.com
  • Authorized redirect URI: https://coolify.shadowarcanist.com/auth/google/callback
  • Hosted domain hint: shadowarcanist.com (optional)

Set up Google OAuth

Select a Google Cloud project

Open the Google Auth Platform and select or create the Google Cloud project that will own the OAuth client.

If Google asks you to configure the consent screen, complete Branding, choose the appropriate Audience, and add contact information. For an external app in testing, add every person who will test Coolify as a test user.

Create a web OAuth client

Open Clients, select Create client, and choose Web application as the application type.

Enter a name such as Coolify. Under Authorized redirect URIs, add:

https://coolify.shadowarcanist.com/auth/google/callback

Create the client.

Save the Google credentials

Copy the generated Client ID and Client secret. You can also download the client JSON, but Coolify only needs these two values.

Configure Google in Coolify

Open Settings > OAuth and find Google.

Coolify fieldGoogle value
Client IDThe Google web client ID.
Client SecretThe Google client secret.
Redirect URIhttps://coolify.shadowarcanist.com/auth/google/callback
TenantOptional hosted-domain hint, such as shadowarcanist.com.

Select Save, then turn on Enabled for Google.

Tenant is a login hint, not an access rule

The Google Tenant value supplies the OAuth hd parameter. It can guide the account chooser, but Coolify does not use it to enforce that the returned email belongs to that domain. Restrict users in Google and in Coolify.

Verify Google sign-in

Open the Coolify login page in a private browser window and select Login with Google. Complete consent if requested, then confirm that Coolify opens the account matching the Google email address.

Troubleshooting

On this page