AEM 6.3 Chrome Error Message

[surendarm613658]

I support AEM 6.3 version and one of site which is hosted in AEM is getting below error message while launching in chrome but same link is opening in IE without any issues. It looks like somewhere in AEM it is configured as "http" which is preventing to launch the site.

Can you please guide me where exactly this can be verified in AEM?

I have indicated XXX which is the URL of the site but due to privacy mentioned it as XXX.

Error Message:

Mixed Content: The page at 'https:XXXXXXXXXX' was loaded over HTTPS, but requested an insecure resource 'http://XXXXXX'. This request has been blocked; the content must be served over HTTPS.

[surendarm613658]

Team - Any suggestions please

[Mayank_Gandhi]

Mixed Content is content on a secured site which is not secure. For a secured/encrypted website; its content such as text, images, videos, objects, scripts, link, iframe, etc… that is being delivered over HTTP instead of HTTPS. If any of content loads over HTTP or mixed with HTTP & HTTPS, it is called Mixed Content – or partially encrypted content. Web browsers such as Google Chrome, Mozilla Firefox, and Internet Explorer, etc… identify Mixed Content loaded over the website and display warnings with red/yellow triangle on the padlock icon in URL/address bar which is called a Mixed Content Error Message.

You need to fix the http:// URLs listed in the error, Try changing the siteUrl from http:// to https://

Ref Preventing Mixed Content  |  Web Fundamentals  |  Google Developers

[surendarm613658]

Thanks Manayak. Can you please suggest how to change the site URL? Because on the AEM i have access to content site where i can edit/change the site content but not sure exactly where to change the site URL.

[Mayank_Gandhi · Accepted solution]

Hi,

It will be manual effort to identify why the resource is being loaded insecurely, below link provide in-depth detail on what to look for. This is how the browser runs to check on any site to prevent mixed content, it's not specific to the product. So you refer to any public document, in this case, to identify and fix the issue, Guidelines for the same are shared in below documents:

https://really-simple-ssl.com/knowledge-base/how-to-track-down-mixed-content-or-insecure-content/

Preventing Mixed Content  |  Web Fundamentals  |  Google Developers