AEM Cloud Dispatcher is ignoring the vhost files | Community
Skip to main content
P
pasridharan
Level 2
March 10, 2023
Solved

AEM Cloud Dispatcher is ignoring the vhost files

  • March 10, 2023
  • 6 replies
  • 2890 views

My dispatcher code is working fine on local docker but the same does not happen on cloud as I could not see my custom vhost getting invoked. I could not change the name of the default vhost as it throws error during build as validation. Pages gives 404 with log giving blocked error when using domain url. I tried allowing things on filter but nothing helps

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 somen-sarkar

Hi, 

Are you able to validate the code in your local instance ?  Recommend to validate the config and then generate the same in an out folder. Later use the out folder cofigurations to start the docker and check the functionalities in local instance before deploying to cloud. 

 

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/content-delivery/validation-debug.html?lang=en#local-validation-flexible-mode

 

Thanks,

Somen

6 replies

aanchal-sikka
Community Advisor
aanchal-sikkaCommunity Advisor
Community Advisor
March 10, 2023

Hello @pasridharan 

 

Can you possibly share how the dispatcher file structure looks for you currently?

Aanchal Sikka
    P
    pasridharanAuthor
    Level 2
    March 10, 2023

    Hi,

     

    Its exactly similar to https://github.com/adobe/aem-guides-wknd/tree/main/dispatcher/src. I'm using windows machine to generate symlink. I can see the enabled host and enabled farm with symlink on the git and Azure repo

      aanchal-sikka
      Community Advisor
      aanchal-sikkaCommunity Advisor
      Community Advisor
      March 10, 2023

      Hello @pasridharan 

       

      Will it be possible for anyone with a mac machine to generate symlinks and push them to git?

       

      Aanchal Sikka
        somen-sarkar
        Community Advisor
        somen-sarkarCommunity AdvisorAccepted solution
        Community Advisor
        March 10, 2023

        Hi, 

        Are you able to validate the code in your local instance ?  Recommend to validate the config and then generate the same in an out folder. Later use the out folder cofigurations to start the docker and check the functionalities in local instance before deploying to cloud. 

         

        https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/content-delivery/validation-debug.html?lang=en#local-validation-flexible-mode

         

        Thanks,

        Somen

          P
          pasridharanAuthor
          Level 2
          March 10, 2023

          yes in local things works fine. I'm able to see out folder and url shortening are working fine

            Himanshu_Jain
            Community Advisor
            Himanshu_JainCommunity Advisor
            Community Advisor
            March 10, 2023

            Try to add your changes directly in available vhost file just for testing .

            Himanshu Jain
              Jagadeesh_Prakash
              Community Advisor
              Jagadeesh_PrakashCommunity Advisor
              Community Advisor
              March 10, 2023

              @pasridharan 

               

              Can you check if your dispatcher is compiling with below command and also check if the files are populating in out folder.

              bin\validator full -d out src

               

              if still it is not working once check in the logs for error and share it here 

               

               

                P
                pasridharanAuthor
                Level 2
                March 10, 2023

                Hi, Yes my dispatcher code on local is compiling and getting build and the url shortening are working fine in local without error and we have tested the pages with shortened url with local docker which also stores the cache files. however, on cloud, I'm facing request url not found with 404

                  V
                  Adobe Employee
                  vivekanand-mishAdobe Employee
                  Adobe Employee
                  March 10, 2023

                  @pasridharan You have not provided enough details to suggest anything. Always add proper details/ snapshots to issue. 

                   

                  1. throws error during build as validation- What error? Put log trails to identify root cause.

                  2. Pages gives 404 with log giving blocked error-  Again no trace to error

                   

                  My guess is that you have not done all necessary configurations needed to enable a new vhost. Read through this document to understand if your farm is configured properly to serve the desired domain - [0]

                   

                  Also, you should enable trace logging to debug this better- [1]

                   

                  [0]- https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/dispatcher-configuration.html?lang=en#identifying-virtual-hosts-virtualhosts 

                  [1]- https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/dispatcher-configuration.html?lang=en#logging 

                    SantoshSai
                    Community Advisor
                    SantoshSaiCommunity Advisor
                    Community Advisor
                    March 11, 2023

                    Hi @pasridharan ,

                    You should not change anything file named default_ as. You can read there is note inside the file 

                    DO NOT EDIT this file, your changes will have no impact on your deployment.

                    As per the documentation, 

                    https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/content-delive...

                    You should create your custom vhost in available directory, and include custom host file and then put your logic in that, make that custom.
                    Also, worth reading this article for Read Only or Immutable files: https://experienceleague.adobe.com/docs/experience-manager-learn/ams/dispatcher/immutable-files.html?lang=en

                     

                    Hope that helps!

                    Regards,

                    Santosh

                     

                    Santosh Sai
                      Terms & ConditionsAccessibility statement

                      Loading footer...