## Documentation

- About
- Read First
  - What is IdentityServer
  - Installation Scenarios
- Migrations
- Bootstrapping
- Configuration & Integration
  - AdminUI Settings
  - Configuring AdminUI
  - Configuring AdminUI (NuGet)
  - Integrating with Identity Server
  - Integrating with Identity Server Custom Schema
  - Integrating with Quickstarts
  - Enabling Logging
- Installation
  - Installer
  - IIS
  - Azure
    - Install in Azure
    - Create Azure Web App
  - Docker
  - NuGet
- Custom Database Connections
- Custom Identity Store
  - Overview
  - Partial Implementation
  - Full Implementation
  - Tenancy With Entity Framework
  - NoSql Implementation (MongoDB)
- Custom CSP
- Users
  - Searching for Users
  - Adding Users
  - Editing Users
  - Deleting Users
  - Merge Users
  - Set User Password
  - Session Management
  - User Reports
  - Bulk User Import
- Roles
  - Creating Roles
  - Managing Roles
  - Managing Users in a Role
  - Managing Role Claims
- Claim Types
- Clients
  - Searching for Clients
  - Adding Clients
  - Adding a SAML Client
  - Adding a WS-Fed Client
  - Editing Clients
  - Deleting Clients
  - Clone Client
- Import and Export
  - Exporting Clients
  - Importing Clients
  - Importing Client Configuration with Secrets
  - Importing SAML Clients with Certificates
  - Import and Export Via the API
- Dynamic Authentication Providers
  - What is Dynamic Authentication
  - Enabling or disabling Dynamic Authentication
  - Add a Dynamic Provider
    - First Steps
    - Adding OIDC Provider
    - Adding SAML Provider
  - Edit a Dynamic Provider
    - Accessing edit view
    - Editing a OIDC Provider
    - Editing a SAML Provider
  - Deleting a Provider
  - Searching for Provider
- Resources
  - Searching for Resources
  - Creating Resources
  - Editing resources
- Webhooks
  - Webhooks
  - Endpoint Configuration
- User Settings Endpoints
- Access Policy
- Keys
- Auditing
- FAQs
- Troubleshooting
  - Unable to start AdminUI
  - Unable to contact IdentityServer
  - Unable to contact API
  - Unable to log in

### Unable to contact IdentityServer

- -Does the OpenID Connect discovery document work?
- -Discovery document does not load
- -Discovery document loads
- -Check the IdentityServer logs
- -Check your configuration
- -Check the AdminUI logs
- -Support

If you experience the error message “Unable to contact IdentityServer”, it means that the AdminUI backend cannot successfully communicate with IdentityServer.

To troubleshoot this issue, we recommend working through the following steps.

## Does the OpenID Connect discovery document work?

You can verify that your IdentityServer can start-up and access your database by navigating to the OpenID Connect discovery document in your browser, available on the IdentityServer 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 IdentityServer logs.

### Discovery document loads

If your discovery document does load, then the next step is to determine why IdentityServer denied the request.

## Check the IdentityServer logs

Depending on your IdentityServer setup, IdentityServer will be logging failed incoming requests. To enable logging, check out our logging documentation. If you are using your own IdentityServer, we recommend following the Microsoft documentation for logging.

## Check your configuration

If you are not seeing any logged requests made to IdentityServer, it may be that AdminUI is not pointing at your IdentityServer. 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 IdentityServer 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 IdentityServer, 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@identityserver.com, detailing the issue you see, including any error logs.

Previous Next