Expand my Community achievements bar.

Guidelines for the Responsible Use of Generative AI in the Experience Cloud Community.
SOLVED

SSL URL and Public IP not showing site content from AEM Dispatcher

Avatar

Level 2

Our AEM site content is not showing up when hitting the SSL address and our public IP from our Dispatcher webserver using IIS. The content is generated successfully on the author instance, it gets replicated successfully on the dispatcher instance at http://localhost:4503/content/xyz/en/webpage.html, and our dispatcher flush agent is working properly. I also have SSL installed and a public IP configured..

 

When I view the website on the SSL URL https://localhost/content/xyz/en/webpage.html on dispatcher, or the public IP URL https://123.123.123.123/content/xyz/en/webpage.html , the page is loading successfully but it's missing the interactive content

 

 

Here is the content on the http://localhost:4503 address on Dispatcher

Content on Localhost Dispatcher.png

 

 

Here's the content not showing on the SSL address and public IP

Content on public IP address.png

 

 

1 Accepted Solution

Avatar

Correct answer by
Level 2

I fixed the dict.en,json and userinfo.json errors by adding folder path exceptions to the filter list in the dispatcher.any file according to this link https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/getting-started/security...

 

and then I fixed the SearchAssets error by doing the following:

Adding this line to system.web block in the web.config file resolved the problem:

<httpRuntime requestPathInvalidCharacters="" />

View solution in original post

4 Replies

Avatar

Level 2

Are there any logs I can look at and identify the content being blocked when loading the SSL webpage?

Avatar

Correct answer by
Level 2

I fixed the dict.en,json and userinfo.json errors by adding folder path exceptions to the filter list in the dispatcher.any file according to this link https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/getting-started/security...

 

and then I fixed the SearchAssets error by doing the following:

Adding this line to system.web block in the web.config file resolved the problem:

<httpRuntime requestPathInvalidCharacters="" />

Avatar

Administrator

@AEM_user25 Thank you for sharing the solution with AEM Community, with would help in posterity. 



Kautuk Sahni

Avatar

Level 2

In the network developer tools I found the dict.en.json, userinfo.json are 404'ing on https://localhost/content/xyz/en/webpage.html

image.png

 

 

but they're all green on http://localhost:4503/content/xyz/en/webpage.html

image2.png