503 and the usual methods don’t work. HELP please

  • We have tried EVERYTHING. Staging site, even another site in another account (same host though ) Flipping off all the plugins, switching to a default theme. Resaving permalinks. Replacing htaccess. Repair and optimizing the database and deleting anything pertaining to no longer used plugins. I even tried disabling Wordfence and Mod Security.
    We have nonstop json errors, and console often says stuff like this is blocked, even when not getting an overall 503. wp-json/wp/v2/ or admin-ajax are throwing 503. I feel these might be ‘blocked’ by something on the server, but won’t get any help from hosting unless we can give details on where to look, and that is just a guess because I can’t find anything in WordPress itself to cause it.

    I’ve found nothing especially useful in the search engines as it just redirects me to the ‘beginner’ steps I’ve already tried. So I desperately hope someone here has an idea.

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)

  • Hello there,

    The 503 error usually means that server is overloaded, and the requests time-out because of that, if your site has cPanel on that A2 Hosting, can you check resource usage in cPanel? Also, check the traffic data, maybe bots are “hitting” your site and “eating” resources. Is your site hosted on a shared hosting environment?

    From the WordPress side you can use the https://www.ads-software.com/plugins/query-monitor plugin to see if there is something that creates long queries which are overloading the server.

    Check that and let’s see if there is more helpful information.

    Kind Regards.

    Thread Starter Starhorsepax2

    (@starhorsepax2)

    We have tried all that. We even got Code Profiler Pro. And as I said, I tried disabling absolutely everything. There aren’t enough hits from site users to explain what is causing it, the only thing I see loads of is those json hits. And that is just us trying and being unable to edit the site.
    And it sure wouldn’t explain the deal on the other account. The other account has little but contact info on its website, yet putting this site in a subfolder where NO one can find it but us (hence an ideal place to test), still causes the 503 issues. (It is the same webhost).

    It’s the hosting issue then, check if you can see the resource usage in the cPanel, I bet it’s at 100%.

    You would be wasting time trying to figure out something which is on the hosting end, you can clone site to another hosting, or another IP address, just to test it, and then you will know for sure that it’s the hosting problem.

    Shared hosting environments are usually like that, shared hosting with shared resources, is oversold to many people and then this happens, do you know that there are hundreds of websites sharing that IP address and sharing resources? You can see it here -> https://2ip.io/domain-list-by-ip/70.32.23.105/

    Kind Regards.

    Thread Starter Starhorsepax2

    (@starhorsepax2)

    Odd thing is we do have other sites on there in that shared hosting and only this one is doing it. I was actually wondering though if it could be something to do with Immunify. I noticed something in there that it kills scripts it thinks are attacks. I wonder if somehow, it’s gotten the idea we, the administrators, are the attacks. Unfortunately, we don’t have access to turn off the setting to test.

    If you are using Imunify – it’s possible that something from there block the scripts, but if the script is blocked you should get 403 errors, 503 are classic time-outs, but these time-outs can be a result of a long request or some kind of a loop. In any case, cloning the site to another IP would help you to isolate the problem.

    Kind Regards.

    Thread Starter Starhorsepax2

    (@starhorsepax2)

    If we put this on another IP it’s staying there. A2 is being VERY UNHELPFUL.

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.