Common problems with LaunchDarkly

When you add the integration

What you see	What to do
The field "API URL" is required.	Type https://app.launchdarkly.com/api in API URL.
API URL must be a full address starting with https://, for example https://app.launchdarkly.com/api.	The address lacks https://. Type https://app.launchdarkly.com/api in API URL.
The field "LaunchDarkly token" is required.	Paste the access token in LaunchDarkly token.
app.launchdarkly.com refused the credentials (401). Check the token, and that it has not expired. Fix the field above, or save anyway if the source is only unreachable for now.	The token is wrong or expired. Create a new token with the reader role in LaunchDarkly and paste it.

When the license does not cover LaunchDarkly

What you see	What to do
In Administration › Plugins, the LaunchDarkly card says Requires the Premium license, and Configure is grey	LaunchDarkly is part of the Premium license. Click the line, add a license that covers it, then switch the plugin on.
On the LaunchDarkly tab of a component, Your license does not cover LaunchDarkly. or The license could not be checked.	Add a license that covers LaunchDarkly in Administration › Licensing, or try again in a minute. Not verified on an instance yet: the tab is not shown once the license no longer covers LaunchDarkly.

On the LaunchDarkly tab of a component

What you see	What to do
LaunchDarkly is not configured yet This plugin is running but has nothing to show until it is configured from the administration. Missing or invalid: API URL, API key	Click Open the LaunchDarkly settings, fill in API URL and API key, click Save, then Reload.
LaunchDarkly refused the API key. The key may have expired, been revoked or lack read access: enter a valid one in the LaunchDarkly settings.	Click Open the LaunchDarkly settings, paste a valid API key, click Save, then Reload. Then check that the component has its launchdarkly.com/project-key annotation.

After you add the integration

What you see	What to do
On the LaunchDarkly card of Company connections, Not working	Click Manage. The State column says why: for example app.launchdarkly.com refused the credentials (401). Check the token, and that it has not expired. Click Edit Token and paste a new token.
In Administration › Problems, a Company connection line LaunchDarkly: app.launchdarkly.com refuses the credentials (401). The token may be wrong or expired.	Click Fix it: it opens the integration. Paste a new token.

Still stuck?

Write to support@forgeit.fr with the name of the component and the message you see.