Diagnostics and Troubleshooting


When troubleshooting on a live environment, you would do not have the source code of the application deployed.

Problems: If you encounter any of the following problems:

  • You are not able to log into the Sitefinity instance
  • You get a No contract for communication found error when editing a .NET Core page.
  • You get the Invalid value for identity server host header passed YSOD.

Solution: The above problems are most likely related to incorrectly setup of the .NET Core Renderer application. To fix them, make sure that your Sitefinity CMS instance and your .NET Core Renderer application are correctly set up. Make sure you perform correctly the steps in the Setup procedure.

Solution: Alternatively, you can get more detailed information whether the .NET Core Renderer is set-up correctly, using the Diagnostics section below.

Problem: You are having runtime errors

Solution: You can search the cause of the errors in the logs of the application. To do this, you must access the logs in one of these ways:

  • If you are hosting on Microsoft Windows, you can look in the Application Event Log (IIS).
  • Alternatively, you can add a file system logger to catch the logs. You can implement your own or use a third-party logger, such as Serilog.


If you cannot identify the reason why your Renderer app is not working, you can run the diagnostics page.

  1. Enable the .NET Core Renderer diagnostics.
    To do this, open the web.config file of your Sitefinity CMS instance.
  2. Inside section <configuration> / <appSettings> insert the following:
    <add key="sf:enableRendererDiagnostics" value="true" />

    NOTE: You should enable this setting only for debugging purposes.

  3. Run the Renderer in debug mode with environment Development.
    If you have not changed it, this is the default value.
  4. Navigate to the diagnostics using the following URL:
  5. If you want to view the request that is reaching the .NET Core Renderer for debug purposes, navigate to https://localhost:5001/sfrenderer/diagnostics/requestdump

Page diagnostics

Sitefinity .NET Core Renderer supports diagnosing the page for performance problems.

For page diagnostics, you do not have to setup Sitefinity CMS, using the procedure above.

PREREQUISITES: You must be in development environment

To diagnose a page, you must include the ?sfdiagnostics query parameter in the page URL.
A value for the query parameter is not required.

RESULT: When the page is executed with the query parameter, each widget is profiled for the requests made through the HttpClient interface. The time for the widget execution is logged as well.

The following screenshot displays a sample result:


In the example above, you can see the following:

  • The total Page execution time - 411.1505ms
  • The preparation requests for the page – current user, current site, batch requests, and their duration
  • Request trace and execution time for each View Component
    In this case, ContentList - 4.2536ms, Navigation - 1.0173ms

    NOTE: The times are fast, because the data was fetched in the preparation stage, prior to executing the page.

  • In the last section - All Requests, you can see the requests made by both preparations and widgets

Increase your Sitefinity skills by signing up for our free trainings. Get Sitefinity-certified at Progress Education Community to boost your credentials.

Get started with Integration Hub | Sitefinity Cloud | Sitefinity SaaS

This free lesson teaches administrators, marketers, and other business professionals how to use the Integration hub service to create automated workflows between Sitefinity and other business systems.

Web Security for Sitefinity Administrators

This free lesson teaches administrators the basics about protecting yor Sitefinity instance and its sites from external threats. Configure HTTPS, SSL, allow lists for trusted sites, and cookie security, among others.

Foundations of Sitefinity ASP.NET Core Development

The free on-demand video course teaches developers how to use Sitefinity .NET Core and leverage its decoupled architecture and new way of coding against the platform.

Was this article helpful?