The Issue has been Resolved by adding the allow  IP in the farm file rather than the invalidate_any file. For some Reason AEMaaCS local setup IP need to be mentioned in the farm file rather than the invalidate_any file.

@TarunKumar @Jagadeesh_Prakash , I am getting the same error when flushing using curl on local docker dispatcher. curl -k -H "CQ-Action: DELETE" -H "CQ-Handle:/content/www" -H "Content-Length: 0" -H "Content-Type: application/octet-stream" http://localhost:80/dispatcher/invalidate.cache <!DOCTYPE HT...

Hi @TarunKumar  the user is an local admin and i am testing this on my local dispacther setup so there is no issues related to access on AEM. The error message is saying flushing has been rejected from the IP through everything is allowed.

Yes i have followed the same steps as outlined below. Below is how my dispatcher is being run.   ~/dispatcher-sdk-2.0.169  DISP_LOG_LEVEL=Debug REWRITE_LOG_LEVEL=Debug ./bin/docker_run.sh /Users/ragucis/Downloads/aem-guides-wknd-aem-guides-wknd-3.2.0/dispatcher/src host.docker.internal:4503 80 ...

i did try allowing all IP's with like you mentioned but still have the same issue.

Hi,I am trying to set up a local dispatcher to debug some issue I have the flush agent set up on author AEM instance and my dispatcher is running on the Docker container. However, when I try to test the connection and getting a 403 error, I tried to add the local host and IP of the author instance ...

Is that how its done for the cloud ? per adobe documentation it said we need to setup a docroot for each site and dispacther from the documentation below https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/dispatcher-domains.html?lang=en

Thats just my naming convention, i does not directly correlate to the AEM stage and PROD on cloud. I do have multiple sites in the same environment.  

hi @Jagadeesh_Prakash  I have already done this and my enable_vhosts files or enable_farm files are loading in the correct order and i have then numbered like 001_wwfarm and 002_stagefarm . The invalidation seem to be going to right path when coming the domain name is attached and TTL expires , only...

i have added the values localhost”, “.local”, “.adobeaemcloud.com”, and “.adobeaemcloud.net in the virtual host section of both farm but it did not work the farm selection does not seem to work when invalidating the cache between different content sites. I found this link but i am not sure how this ...