Docs

Troubleshooting

Fix the most common setup problems when connecting an application to Clikkle Identity.

Sign-in button is disabled

Confirm your running application has the Client ID generated by Console in the environment configuration used by that framework. If the framework reads environment variables at build time, restart or rebuild after changing them.

Application is not authorized

Confirm the application is Active and that your app is sending the exact Client ID shown in Console. Do not create a second application unless you intentionally need a separate client.

Redirect URI rejected

Compare the browser callback URL with Authorized redirect URIs in Console character-for-character. Check scheme, hostname, port, path and trailing slash.

Origin rejected

Add the exact browser origin to Allowed web origins. Do not include a path in an origin.

Changed an environment variable but nothing changed

Confirm you edited the environment source your project actually loads, then restart the development server. For production frontends that embed environment variables during build, create a new production build and deploy it.