Configure Discord OAuth

Create a Discord application so Coolify can request the identify and email scopes during sign-in.

Example data

Replace the example domain while following this guide:

  • Coolify URL: https://coolify.shadowarcanist.com
  • Redirect: https://coolify.shadowarcanist.com/auth/discord/callback

Set up Discord OAuth

Create a Discord application

Open the Discord Developer Portal, select New Application, enter a name such as Coolify, and create the application.

The application does not need a bot for Coolify sign-in.

Register the Coolify redirect

Open OAuth2 for the Discord application. Under Redirects, select Add Redirect and enter:

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

Save the changes.

Coolify supplies the identify and email scopes when it starts authorization. You do not need to generate or copy an OAuth URL from Discord.

Copy the Discord credentials

On the OAuth2 or General Information page, copy Client ID.

Copy or reset the Client Secret, then store the complete value securely. Resetting the secret invalidates the previous value.

Configure Discord in Coolify

Open Settings > OAuth and find Discord.

Coolify fieldDiscord value
Client IDDiscord application Client ID
Client SecretDiscord application Client Secret
Redirect URIhttps://coolify.shadowarcanist.com/auth/discord/callback

Select Save, then turn on Enabled for Discord.

Verify Discord sign-in

Coolify identifies an existing user by email address. The email address on the Discord account must match the email address on the Coolify account. Matching is case-insensitive.

Open the Coolify login page in a private browser window and select Login with Discord. Authorize the application, then confirm that Coolify opens the account with the matching email address.

If the email addresses do not match and Registration Allowed is enabled, Coolify creates a new user with the email address returned by Discord instead of signing in to the existing account. If registration is disabled, Coolify rejects the sign-in.

Troubleshooting

On this page