Sure there could be many reasons that a website gets a 508 Resource Limit Reached error message. And the generic answers are what you might have to check into and troubleshoot.
But it sure is helpful when I finally found a customer service agent that could find the specific problem that was causing my website to become unavailable about once a week recently, even when I wasn’t doing anything in particular to edit my WordPress-powered website or update plugins or doing anything intensive, because I literally wasn’t doing anything on the website.
Some articles out there talk about looking at the Resource Usage snapshot or detail, to see the usage levels for CPU, Inotes, I/O, IOPS, Entry Processes, and Physical Memory. Nice graphs and charts to tell you the usage level, but they don’t tell you WHAT is using up those resources. That’s the information we actually need, you know?
In my situation, the problem was a bot attack from Panama. The customer service agent at InMotion Hosting, my current shared web hosting company for djchuang.com (and its add-on sites) looked thru the Activity Log and noticed a barrage of visits from one IP address, and that’s what queued up a ton of requests that used up the web server’s resources.
They explained, “I see hundreds of requests for different files from the same IP and user agent. That can fill up the entry processes which in turn spawns the 508 error.”
Stopping Bot Attacks in Cloudflare
The customer service agent suggested, “You might want to look into something like Cloudflare which has a very robust bot and automated attack prevention systems. They have a free tier which is what most people would need on their sites as their paid versions are more geared toward enterprise-level systems.”
And, good thing, that’s where I have my DNS for my website. I went over to Cloudflare, and made sure to turn ON the setting for Bot Fight Mode with all my websites. (under website > Security > Bots > Bot Fight Mode)
(Hopefully that’ll resolve things for weeks and months ahead. I’ll update this blog post if it all goes well, or not.)