Site not loading for a particular path and getting error code 20 | Community
Skip to main content
V
VikramP8
Level 2
December 17, 2024
Solved

Site not loading for a particular path and getting error code 20

  • December 17, 2024
  • 3 replies
  • 792 views

Hi All

 

We have site in the production preview environment assuming url as prev-www.testsite.com/global

 

The site loads fine with all the path example

1. prev-www.testsite.com/global/about

2. prev-www.testsite.com/global/community.

 

And the request is not working only for a specific path (prev-www.testsite.com/global/us) and is shown with error code 20. There is no caching rules implemented.

 

 

When /us path is accessed no logs are even generated in the dispatcher server, but all other paths are working fine.

The server architecture for request is: Browser -> WAF layer -> ALB -> Dispatcher server ->ALB -> Publisher server.

Can you please help me understand what exactly the issue.

 

Thanks.

 

 

    Best answer by VikramP8

    Got the issue resolved. We had a configuration defined in demandbase with site specific authentication. So adding the new site in this config resolved the issue.

    (Site ID=Site group~InternalOnly/InternalGroups/GroupsOnly)

     

    Thanks.

    3 replies

    Kamal_Kishor
    Community Advisor
    Kamal_KishorCommunity Advisor
    Community Advisor
    December 17, 2024

    @vikramp8: Can you check your publisher logs and see if there is some error?

      V
      VikramP8Author
      Level 2
      December 17, 2024

      The request is not reaching the publisher.

      Below i see in the dispatcher when hitting prev-www.testsite.com/global/us  it's taking to /content/login.html.

       


      [pid 18821] response.headers[Location] = "http://prev-www.testsite.com:7000/libs/granite/core/content/login.html?resource=%2Fcontent%2Ftest%2Fglobal%2Fen_us%2Fhome.html&$$login$$=%24%24login%24%24&j_reason=unknown&j_reason_code=unknown"
      [pid 18821] "GET /content/test/global/en_us/home.html" 302 none [pw/rend01] 7ms

      arunpatidar
      Community Advisor
      arunpatidarCommunity Advisor
      Community Advisor
      December 17, 2024

      Hi @vikramp8 

      Seems its failing at WAF die to filtering or custom rules, can you check the WAF rules?

      Arun Patidar
        V
        VikramP8Author
        Level 2
        December 17, 2024

        Sure, will have a check on it.

        Thanks.

        V
        VikramP8AuthorAccepted solution
        Level 2
        December 18, 2024

        Got the issue resolved. We had a configuration defined in demandbase with site specific authentication. So adding the new site in this config resolved the issue.

        (Site ID=Site group~InternalOnly/InternalGroups/GroupsOnly)

         

        Thanks.

          Terms & ConditionsAccessibility statement

          Loading footer...