0

I have a SaaS app where I often use the Wordpress REST API to communicate with the wordpress websites of clients.

It was working perfectly for months but i realized a few days ago that now every request sent from my deployed Render backend server creates an error 503, with these details :

Security check
Sorry, we need to verify that this request is legitimate and is not sent by an automated system (robot).
This verification process is automatic. Your browser will redirect you in a few seconds.

with O2Switch UI around it.

My question is : did some of you got the same problem recently ? Or is it because my render server IP has been blocked ? And if so, do some of you know the best way to fix that, and avoid that it happens again in the future ?

I tested on local server and it works so I still don't really know if it's my render server especially or a global deployed app problem ...

Thanks in advance for your replies !

5
  • I'd reach out to your WP Host as it seems most likely that they're blocking your Render server. Commented Jul 23 at 16:30
  • @TonyDjukic thanks for this ! But then if they do I suppose others might do too don't you think ? So how to handle that ? Commented Jul 28 at 10:31
  • You'd have to ask them to make an exception for it. Or start hosting on a VPS where you have the control over those decisions. I'm not a SysAdmin so hate being in the situation myself, so I tend to look for hosts that are willing to work with me and give individualized instances and not shared hosting. It's the shared hosting that's really strict usually. Commented Jul 28 at 18:46
  • Since your clients can choose where to host you cant have 100% control. The error is not directly from WordPress system its a server security feature. You may ask the hosting company what you may improve to not get blocked as proper user agent , X-WP-Nonce header missing ? they may have some mod_security rules too .. its different and would be hard to fix it. Commented Jul 29 at 12:19
  • Thanks for your replies ! Indeed I found the culprit : one of the IPs used by my server by default had been temporarily blacklisted because shared through many services on the platform where I deployed my backend (render). So I just added a specific IP rolling system for those export requests and now it's working fine ! But thanks for your reply ! Commented Sep 12 at 9:08

1 Answer 1

0

Just found the solution as explained in my commentary in my original post !

The problem was that one of the IPs used by my server by default had been temporarily blacklisted (because shared through many clients) on the platform where I deployed my backend (Render).

So I just added a specific IP rolling system for those export requests and now it's working perfect, so maybe try it out or at least check your app's IP status !

Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.