If you have a multisite Sitefinity CMS instance and you have configured more than one site in a your Sitefinity instance, you have to further configure the domains of the frontend for both the Sitefinity CMS application and the ASP.NET Core Renderer.
NOTE: If you have a single site in your Sitefinity instance, then no further configuration is required.
If the Sitefinity CMS instance is hosted on IIS and the domains are placed on the Sitefinity CMS application, you must remove these bindings and place them on the ASP.NET Core Renderer application. These domains must be placed on the Renderer app, regardless of whether it is hosted on the same IIS on the same machine or on a different machine.
Sitefinity CMS application:
When you configure an ASP.NET Core Renderer, these domains must look like this: ASP.NET Core Renderer application:
Sitefinity CMS application: One of the following:
In general, place all the public multisite domains on the ASP.NET Core Renderer app and reserve a single non-public domain for the Sitefinity CMS app.
In this case, the domain management is already placed on the proxy itself and the proxy forwards the specified Host header to Sitefinity CMS. You only need to redirect the proxy to forward the traffic to the ASP.NET Core Renderer app.
Increase your Sitefinity skills by signing up for our free trainings. Get Sitefinity-certified at Progress Education Community to boost your credentials.
The free standalone Web Security lesson teaches administrators how to protect your websites and Sitefinity instance from external threats. Learn to configure HTTPS, SSL, allow lists for trusted sites, and cookie security, among others.
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.
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important