Expand my Community achievements bar.

July 31st AEM Gems Webinar: Elevate your AEM development to master the integration of private GitHub repositories within AEM Cloud Manager.
SOLVED

Dispatcher deployment failed on AEM as a Cloud Service

Avatar

Level 2

I am getting the following error when I try to deploy my AEM project on Cloud Manager. 

The following errors were found in the httpd config:
  conf.d/available_vhosts/default.vhost:12: included file (conf.d/variables/custom.vars) does not match any known file

I tried running the validator script on the dispatcher locally and I got a few warnings along with this error. I have checked the file names as well as path and everything seems right. Not sure how to fix this error 

 

 

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Level 9

@parth3 

I'm not fully sure that it will solve your problem but you can try some debugging steps from this documentation. 

https://experienceleague.adobe.com/en/docs/experience-manager-learn/cloud-service/debugging/debuggin...

View solution in original post

5 Replies

Avatar

Correct answer by
Level 9

@parth3 

I'm not fully sure that it will solve your problem but you can try some debugging steps from this documentation. 

https://experienceleague.adobe.com/en/docs/experience-manager-learn/cloud-service/debugging/debuggin...

Avatar

Community Advisor

Hi, 


Do you have the file custom.vars? What is its content? Do you see any syntax issues in it?

EstebanBustamante_0-1716950428538.png

 



Esteban Bustamante

Avatar

Community Advisor

Hi @parth3 

  1. Check the file path: Double-check that the file path for custom. vars is correct and that the file exists in the specified location. If the file is not in the correct location, move it to the correct location and try deploying your project again.

  2. Check the file name: Make sure that the file name is spelled correctly and that it matches the name specified in the configuration file. If the file name is incorrect, update the configuration file to use the correct file name.

  3. Check the file permissions: Ensure that the file has the correct permissions set so that it can be read by the Apache HTTP Server. You can check the file permissions by running the command Is -1 in the directory where the file is located.



Avatar

Employee Advisor

have you switched on flexible mode?

Avatar

Administrator

@parth3 Did you find the suggestions from users helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.



Kautuk Sahni