1

Sitecore support advised: The issue is a bug with reference number 439986. As a workaround for the issue, please try adding the following section: </security> <defaultDocument> <files> <clear /> <add value="Default.aspx" /> </files> </defaultDocument> </system.webServer> in the "web.config" ...


1

I had faced the same issue during the installation of Sitecore 9.3. It was because the certificate already exists with the same Sitecore instance name in my machine. I have followed the below steps to get rid of this: Removed the certificates from my machine with the same instance name Removed Services Removed the Sitecore instance from the inetpub ...


1

I have also faced similar issue and I fixed that by doing some investigation like below: Check if the certificates are present and valid in the xconnect site. If it is invalid or expired, generate those and assign it to the site bindings. Check if the xconnect site is accessible through HTTPS. Delete the Non-SSL certificate from Root. Check if the sitecore ...


Only top voted, non community-wiki answers of a minimum length are eligible