issues setting up aem RDE environment | Community
Skip to main content
V
vashishth47
Level 2
September 25, 2025
Question

issues setting up aem RDE environment

  • September 25, 2025
  • 3 replies
  • 734 views

I am trying to setup adobe AEM RDE environment. 

 

Have followed the steps mentioned in the following documentation https://experienceleague.adobe.com/en/docs/experience-manager-learn/cloud-service/developing/rde/how-to-use.

 

I ran the "mvn clean package" command and then proceeded to run the command in the screenshot attached below("command run" file). Note I have two different project in my repo.

 

I have also created a new dispatcher for RDE environment and added a symbolic link for the same in the active vhost folder. Added the lines present below in my screen shot. 

 

However whenever I try to hit a servlet it only gives default apache output as 

<html><body><h1>It works!</h1></body></html>.
Please let me know if anything else is required.

 

 

    3 replies

    Tof_Jossic
    Adobe Employee
    Tof_JossicAdobe Employee
    Adobe Employee
    September 25, 2025

    @vashishth47 you'll want to post this in the AEM community: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/bd-p/adobe-experience-manager-qanda 

      SantoshSai
      Community Advisor
      SantoshSaiCommunity Advisor
      Community Advisor
      September 25, 2025

      Hi @vashishth47,

      In your dispatcher config, the wildcard *.adobeaemcloud.com is not being matched. The RDE validator doesn’t allow unrestricted wildcards. You need to explicitly list the exact hostnames that Cloud Manager assigns to your RDE Publish service.

      Example:

      ServerAlias publish-p124507-e1263256.adobeaemcloud.com
ServerAlias myai-rde.adobeaemcloud.com

      You can check your assigned RDE domain under Cloud Manager > Environments > RDE > URLs.

       

      • Try to remove or replace the wildcard:

        ServerAlias *.adobeaemcloud.com

        with the exact domain(s) that Adobe gave you for your RDE publish instance.

      • Make sure your dispatcher/src/conf.d/enabled_vhosts/ folder has a symlink pointing to your new vhost config file. Example:

        cd dispatcher/src/conf.d/enabled_vhosts ln -s ../available_vhosts/my-ai-publish.vhost my-ai-publish.vhost
      Santosh Sai
        VishalKa5
        VishalKa5
        Level 5
        September 26, 2025

        Hi @vashishth47 ,

        You’ve set up your RDE, deployed code, and added dispatcher configs, but when you hit the site you only see the default Apache page. That means your dispatcher isn’t pointing requests to AEM Publish yet.

        VirtualHost config – make sure your <VirtualHost *:80> block has the correct ServerAlias (the exact domain you are using in the browser). Right now, *.adobeaemcloud.com may not match – add the exact RDE publish URL from Cloud Manager.

        Dispatcher farm mapping – check that your dispatcher farm has a renders section pointing to the AEM publish instance (localhost:4503 inside dispatcher).

        Enable vhost – ensure the symlink is placed in enabled_vhosts (not just available_vhosts).

        Flush cache / restart dispatcher – after changes, clear dispatcher cache and restart so config is picked up.

        your dispatcher is serving its own Apache default page because it’s not routing traffic to AEM Publish. Fix the vhost alias + farm renders, then you’ll see AEM content instead of It works!.

        Terms & ConditionsAccessibility statement

        Loading footer...