Dispatcher Flush 403 Error | Community
Skip to main content
R
RanjithreddyGu
January 18, 2024
Solved

Dispatcher Flush 403 Error

  • January 18, 2024
  • 4 replies
  • 3213 views

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 in the client list but still seeing the same error any pointers here? seeing the same error any pointers here? 

 

[core:notice] [pid 1:tid 281473475915864] AH00094: Command line: 'httpd -d /etc/httpd -f /etc/httpd/conf/httpd.conf -D FOREGROUND -D ENVIRONMENT_DEV' [Thu Jan 18 20:52:04.446299 2024] [dispatcher:debug] [pid 283:tid 281473457761024] [client 192.168.65.1:39089] Found farm publishfarm for localhost, referer: about:blank [Thu Jan 18 20:52:04.446348 2024] [dispatcher:debug] [pid 283:tid 281473457761024] [client 192.168.65.1:39089] checking [/dispatcher/invalidate.cache], referer: about:blank [Thu Jan 18 20:52:04.446392 2024] [dispatcher:warn] [pid 283:tid 281473457761024] [client 192.168.65.1:39089] Flushing rejected from 192.168.65.1, referer: about:blank 192.168.65.1 "localhost" - [18/Jan/2024:20:52:04 +0000] "GET /dispatcher/invalidate.cache HTTP/1.1" 403 199 "about:blank" "Jakarta Commons-HttpClient/3.1" [18/Jan/2024:20:52:04 +0000] "GET /dispatcher/invalidate.cache HTTP/1.1" 403 none [publishfarm/-] 1ms "localhost"

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 RanjithreddyGu

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.

4 replies

Jagadeesh_Prakash
Community Advisor
Jagadeesh_PrakashCommunity Advisor
Community Advisor
January 19, 2024

@ranjithreddygu  What are the steps that you followed to run dispatcher on Docker container?

 

FYI hope you followed below steps before you start your docker dispatcher instance ?

https://experienceleague.adobe.com/docs/experience-manager-learn/cloud-service/local-development-environment-set-up/dispatcher-tools.html?lang=en

 

 

    R
    RanjithreddyGuAuthor
    January 19, 2024

    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

      

      TarunKumar
      Community Advisor
      TarunKumarCommunity Advisor
      Community Advisor
      January 19, 2024

      Hi @ranjithreddygu ,

      This is mainly due to IP address through which you are allowing to trigger flush is not allowed.
      For more info. on it you can have look into below article:-
       https://sourcedcode.com/blog/aem/how-to-setup-the-aem-dispatcher-flush-agent


      You can try to add below in your dispatcher file for time being:-

       

      # The allowedClients section restricts the client IP addresses that are
# allowed to issue activation requests.
/allowedClients
{
# deny all clients
/0000 { /glob "*" /type "allow" }
}



      Thanks
      Tarun
       

        R
        RanjithreddyGuAuthor
        January 19, 2024

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

          R
          RanjithreddyGuAuthor
          January 24, 2024

          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.


          @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 HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>403 Forbidden</title> </head><body> <h1>Forbidden</h1> <p>You don't have permission to access this resource.</p> </body></html>
            kautuk_sahni
            Community Manager
            kautuk_sahniCommunity Manager
            Community Manager
            February 2, 2024

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

            Kautuk Sahni
            R
            RanjithreddyGuAuthorAccepted solution
            February 12, 2024

            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.

              Imran__Khan
              Community Advisor
              Imran__KhanCommunity Advisor
              Community Advisor
              February 11, 2024

              This is because of wrong credentials as Apache is password protected. 

               

                Terms & ConditionsAccessibility statement

                Loading footer...