ERROR 429, nothing in error logs

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Jakub Grufik
    Senior Member
    • Aug 2022
    • 361

    ERROR 429, nothing in error logs

    Hello guys,
    I am sorry to bother you today with a lot of problems, but I need to resolve this one as it is making our system much slower than we are used to.

    Sometimes when I refresh our CRM system I am getting error 429, but nothing is being stored in the error log. When I get this error, the system is not loaded and we need to refresh it one more time.

    The only thing I found is the dev tools console with a lot of 429 ERRORS. Do you by any chance know, what could be causing this problem? A few days ago I deleted a lot of files from the upload directory in our repository. I think this could be connected with it. Is there any way how to fix this, please?

    Thanks a lot.
    Attached Files
  • Jakub Grufik
    Senior Member
    • Aug 2022
    • 361

    #2
    Click image for larger version

Name:	image.png
Views:	160
Size:	155.8 KB
ID:	89362
    Full resolution screen, sorry for some reason original image is unreadable​

    Comment

    • yuri
      Member
      • Mar 2014
      • 8442

      #3
      You might have disabled cache in Espo, as a consequence you have many requests being made to webserver.

      This error is returned by your webserver. I googled the error number. "HTTP Error 429 is an HTTP response status code that indicates the client application has surpassed its rate limit, or number of requests they can send in a given period of time.​"
      If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

      Comment


      • Jakub Grufik
        Jakub Grufik commented
        Editing a comment
        wow man, you are right, for some reason USE Cache is disabled in the settings, even tho I have not disabled it. Maybe some other admin did without letting me know. I will try to enable it to see if the error will be solved. Thanks a lot man! Appreciate such a quick help!
    • Jakub Grufik
      Senior Member
      • Aug 2022
      • 361

      #4
      yuri no errors after enabling cache, also the system is much much faster than without cache! thanks a lot for the help man! you are god

      Comment

      • esforim
        Active Community Member
        • Jan 2020
        • 2204

        #5
        Not sure if possible but if you have Workflow, perhaps making it Notify you when it is disable for too long or re-enable it automatically. Or perhaps feature request it to be

        Cache is one thing that unless for testing I see no reason to have it disable for long period.

        Comment

        • mfkp
          Junior Member
          • Jul 2024
          • 3

          #6
          Reviving this old thread, I set up a new instance of espocrm and it's been working fine for a few days. I only have a few users (using the system very sparingly) and myself and the other users keep getting Error 429. Nobody is spamming too many requests, and I have verified that caching is enabled, so that's not the problem. Is there any way to debut this? I can't even open the Admin AppLog because I get Error 429 on that page too. And looking at the server log file, nothing gets logged about this error 429 and there's barely any activity in that log file anyway because nobody is making requests... I'm at a bit of a loss here, hopefully someone knows where to look next.

          Thanks

          Comment

          • mfkp
            Junior Member
            • Jul 2024
            • 3

            #7
            Actually, it may be a Cloudflare issue (as I use cloudflare DNS in front of this instance), so perhaps Cloudflare is rate limiting the XHR requests... investigating now.

            Comment

            • mfkp
              Junior Member
              • Jul 2024
              • 3

              #8
              Confirmed - it was a Cloudflare issue. Turned off rate limiting for the /api/v1 route and everything works fine again. I'll leave these posts up for anyone who might run into this issue in the future.

              Comment

              Working...