error: immutable file ‘conf.d/dispatcher_vhost.conf’ has been changed!

While setting up Adobe Experience Manager (AEM) as a Cloud Service’s dispatcher SDK on my local Mac machine, following this Adobe documentation, I encountered an error while running the command “./bin/ src”. The error message read “error: immutable file ‘conf.d/dispatcher_vhost.conf’ has been changed!”.

After some research, I found that the issue was related to the access permissions of the file in question. To resolve the problem, I ran the command “chmod 777 conf.d/dispatcher_vhost.conf” on my Mac machine. This successfully allowed me to proceed with my local AEM setup.

But what exactly is “chmod 777”?

In Linux and Unix-based operating systems, “chmod” stands for “change mode” and is used to adjust the read, write, and execute permissions of a file or directory. The number “777” is a three-digit code called the “file mode” or “permission mode”. It represents the permissions for the owner of the file, the group the file belongs to, and all other users.

Here are the details about the 777 permission:

7 is the permission for owner
7 is the permission for group
7 is the permission for others (users)
Each digit in the file mode is a sum of the values for the read (4), write (2), and execute (1) permissions. So, 777 means that the owner, the group, and other users all have full read, write, and execute permissions for the file or directory.

It’s important to note that chmod 777 is considered a very open permission, and is not recommended from a security standpoint. It’s generally better to use more restrictive permissions such as 644 for files and 755 for directories, which will still allow the owner to read and write to the file, but prevent others from making any changes. However, for local testing purposes, chmod 777 can be used.

Hello, I am an enthusiastic Adobe Community Advisor and a seasoned Lead AEM Developer. I am currently serving as an AEM Technical Lead at, bringing over a decade of extensive web engineering experience and more than eight years of practical AEM experience to the table. My goal is to give back to the AEM Full Stack Development community by sharing my wealth of knowledge with others. You can connect with me on LinkedIn.

Leave a Reply

Your email address will not be published. Required fields are marked *

Back To Top