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
Here's the content not showing on the SSL address and public IP
Solved! Go to Solution.
Views
Replies
Total Likes
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="" />
Are there any logs I can look at and identify the content being blocked when loading the SSL webpage?
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="" />
@AEM_user25 Thank you for sharing the solution with AEM Community, with would help in posterity.
Views
Replies
Total Likes
In the network developer tools I found the dict.en.json, userinfo.json are 404'ing on https://localhost/content/xyz/en/webpage.html
but they're all green on http://localhost:4503/content/xyz/en/webpage.html