Revision history [back]

There are a few possible reasons why the Swagger UI may not be appearing when an API is deployed on IIS:

1. Incorrect configuration settings: The IIS web server may not be configured correctly to serve the Swagger UI files. Typically, the Swagger UI files are served from a separate endpoint or virtual directory within the application. Ensure that the correct settings are configured in the application's web.config or other configuration files.

2. Missing or incorrect files: The Swagger UI requires certain files, such as the index.html, css, and javascript files, to be present and correctly referenced in the application. If these files are missing or their references are incorrect, the Swagger UI may not appear. Ensure that all necessary files are present and correctly referenced.

3. Authentication or authorization issues: If the API requires authentication or authorization to access, the Swagger UI may not appear if the user does not have the necessary credentials or permissions. Ensure that the authentication and authorization settings are correctly configured and that the user has the required access.

4. Network or firewall issues: If the application is running on a network or behind a firewall, it may be blocking access to the Swagger UI files or endpoints. Ensure that the necessary ports and endpoints are open and that any necessary network settings are configured correctly.

5. Platform or version incompatibilities: Finally, it may be possible that the version of the IIS web server or the platform on which it is running is not compatible with the version of the Swagger UI or the underlying APIs. Ensure that all versions and platforms are compatible and correctly configured.