We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
MODX Community Forums Archive

Answered 403 Errors when manager loads tree with several parent folders open.

    • 39653
    • 13 Posts
    mcyrulik Reply #1, 13 years, 7 months ago
    Hey all,

    I've got kind of a weird one going on here. I've got a site that is MODx version 2.2.4-pl. It has several containers on the resources tab at the top level(16 to be exact). Each of those containers have some resources in them - some even have containers of resources within them. It seems that when you refresh the page, the manager does ajax requests to get the children of the open containers.

    when you have several of those open and I refresh the page, I count at least 26 ajax requests that are being made to URLs similar to "/connectors/resource/index.php?action=getNodes&id=web_211&type=modResource" (I took the domain off for posting here..), the server is returning a "403 - Forbidden" page.

    I talked to the host, and they are going to look though their logs and see if anything jumps out at them, but I'm curious if anyone has seen this before, and if this is a MODx thing, or a server thing. The hosting provider did mention that they have DDOS prevention enabled on their servers, ut it would take 100's of request in less than one second to trigger it, and even then it would return 404 errors, not 403.

    Anyone have any thoughts? It's not really stopping our client from using modx, it's just annoying, and not very comforting...

    ~Mark

    This question has been answered by mcyrulik. See the first response.

      • 8386 ☆ A M B ☆
      • 160 Posts
      Silent Works Reply #2, 13 years, 7 months ago
      I have never gotten this error before, I think it might be host related, can you try and download the entire project and set it up locally and do a test and see if the same issues happen.
        • 28042 ☆ A M B ☆
        • 24,524 Posts
        sottwell Reply #3, 13 years, 7 months ago
        I have at least one site with more folders than that, and I never get such a thing, even with the entire Tree expanded.
          Studying MODX in the desert - http://sottwell.com
          Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
          Join the Slack Community - http://modx.org
          • 40641 ☆ A M B ☆
          • 56 Posts
          chrischerrett Reply #4, 13 years, 7 months ago
          Quote from: sottwell at Feb 13, 2013, 07:26 PM
          I have at least one site with more folders than that, and I never get such a thing, even with the entire Tree expanded.

          Me too. I suspect it's not actually related to the number of resources you have. Sorry I don't have a better answer though.
            • 39653
            • 13 Posts
            mcyrulik Reply #5, 13 years, 7 months ago


            Quote from: chrischerrett at Feb 14, 2013, 02:05 AM
            Quote from: sottwell at Feb 13, 2013, 07:26 PM
            I have at least one site with more folders than that, and I never get such a thing, even with the entire Tree expanded.

            Me too. I suspect it's not actually related to the number of resources you have. Sorry I don't have a better answer though.

            What would count as a lot of resources? This site has 337 resources, 63 chunks, 86 snippets..

            At this point, I may download the site and set it up on a different server and see if it is MODx related or host related, but I suspect it is host related. We have other sites in MODx that do not have this issue.
            • discuss.answer
              • 39653
              • 13 Posts
              mcyrulik Reply #6, 13 years, 7 months ago
              Alright - got this one figured out(we think)..

              The host we are utilizing for this site uses an apache module called mod_evasive as one level of Denial of Service attack protection. One of the things module does is it looks at the number of requests that are coming in to any one page from the same IP over a period of time(one second). In our case, the AJAX requests to build the tree were making more calls to the file /connectors/resource/index.php than mod_evasive would allow, and there fore returning the 403 error.

              ~Mark