If you experience the error message “Unable to contact OpenIddict”, it means that the AdminUI backend cannot successfully communicate with OpenIddict.
To troubleshoot this issue, we recommend working through the following steps.
Does the OpenID Connect discovery document work?
You can verify that your OpenIddict can start-up and access your database by navigating to the OpenID Connect discovery document in your browser, available on the OpenIddict endpoint: https://<your-identity-server>/.well-known/openid-configuration.
Discovery document does not load
If your discovery document does not load, you may instead see an error page containing details on what went wrong. If you do not see any error details, you will need to check the OpenIddict logs.
Discovery document loads
If your discovery document does load, then the next step is to determine why OpenIddict denied the request.
Check the OpenIddict logs
Depending on your OpenIddict setup, OpenIddict will be logging failed incoming requests. To enable logging, check out our logging documentation. If you are using your own OpenIddict, we recommend following the Microsoft documentation for logging.
Check your configuration
If you are not seeing any logged requests made to OpenIddict, it may be that AdminUI is not pointing at your OpenIddict. To confirm that AdminUI is configured correctly, check the AuthorityUrl setting for both the UI and API are the expected value in any web.config (when using IIS/Windows) and appsettings.json files (when using Linux or Kestrel). If you are using an Azure App Service, this can also be set in the App Service’s configuration section.
Check the AdminUI logs
If you are not seeing any logged requests made to OpenIddict and the configuration looks correct, the next step is to check the AdminUI (UI website) logs. This will cover any issues with connecting to your OpenIddict, including certificate validation.
Support
If none of these steps work or you are unsure how to fix the error in the logs, please contact us at support@openiddictcomponents.com, detailing the issue you see, including any error logs.