AEM screen player configuration with Dispatcher | Community
Skip to main content
M
Maddy1104
May 8, 2020
Solved

AEM screen player configuration with Dispatcher

  • May 8, 2020
  • 1 reply
  • 1121 views

Hi All,

I am working on AEM screen project. I have configured AEM screen player with Author and publisher url (ip address) and screen player is working perfectly fine and I can see contents from channel loading properly fine. But when I try to connect screen player with dispatcher url the screen coming blank and no content is loading. I have already followed below URL for dispatcher configuration with screen. Content is loading in browser but in screen player it showing black screen and no content is loading. I am updating dispatcher url from author environment. Thanks in advance.

https://docs.adobe.com/content/help/en/experience-manager-screens/user-guide/administering/dispatcher-configurations-aem-screens.html

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by BrianKasingli

@maddy1104,

Let's debug this problem, can you please answer the questions below?

  1. Have you replicated all appropriate content to the publisher? There may be a chance where content has not been successfully replicated over,
  2. Can you share the error messages captured in the AEM publisher? Sometimes unexpected errors will be surfaced, such as 403 forbidden errors.
  3. Can you share the error messages captured in the Apache webserver? Valuable information will be captured by the webserver. This level of detail will give us a closer understanding of exactly what is happening.

Chances are we a missing a small configuration somewhere, we just need to debug and find the cause. 

1 reply

BrianKasingli
Community Advisor and Adobe Champion
BrianKasingliCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
August 10, 2020

@maddy1104,

Let's debug this problem, can you please answer the questions below?

  1. Have you replicated all appropriate content to the publisher? There may be a chance where content has not been successfully replicated over,
  2. Can you share the error messages captured in the AEM publisher? Sometimes unexpected errors will be surfaced, such as 403 forbidden errors.
  3. Can you share the error messages captured in the Apache webserver? Valuable information will be captured by the webserver. This level of detail will give us a closer understanding of exactly what is happening.

Chances are we a missing a small configuration somewhere, we just need to debug and find the cause. 

    Terms & ConditionsAccessibility statement

    Loading footer...