My Gateway getting hit with 429 even it does only one HTTP request. Its a async message from Gateway when payment is done so i can send emails and process orders. I inspect the issue and i can see that they dont have user agent set, and i believe CF is blocking because of that. I have some rules to allow range of ips but its still hitting. I need help to solve this im using PRO plan
What steps have you taken to resolve the issue?
I set rule for rate limit for speciffict IP but that is not helping.
Thank you for the reply. I am unable to get the body text, since we are in production and I don’t have access to the gateway portal, but during the Test phase I should see the responses from my server to Gateway and indeed it was 429. I will dig deeper to see if I have somewhere in the gpt history. I’m sharing screenshot from the CF dash so u can see. I don’t know what rule to set to avoid this 429. I allowlisted all IPs from the server, but that’s not the issue wince this is a HTTP request. I am getting frustrated with this.
No inside Events i do not see that. Using Origin status code gives me the same thing. There is one thing I just realized. I can create a custom limiting rule where I can set specific URL parameter. This Gateway always calls dynamic URL and I can wildcard it: ?wc-api=wc_allsecureexchange&action=webhook - there is more param appended at the end of the URL, but this should be fine if I set for example 1000 requests per 1 minute, this rule should avoid hitting this PUT request with 429, let me know if I am wrong?
This 429 is not showing in the event list, and as soon as I disable CF I receive a postback message normally. Keep in mind that all server IP ranges are allowlisted and set to skip the default rules of CF. The only thing that comes to my mind is that the User-agent is empty, and that produces instant 429.
I do want to emphasize that as soon as I disable CF this 429 is not happening. Also I have investigated on my WPX directly to see if there I specific Rate limiting rule, but there is not. Gateway server is just sending one message, there is no valid reason to exceed Rate limiting rule.
Nope. That’s an Openresty message. Not a Cloudflare-branded Rate Limiting error.
Every time someone tries to argue the Openresty block is coming from Cloudflare, they eventually find out from the host there’s a firewall the user was not aware of.
Ahaaa, now I get it. Honestly, i don’t want to put this on CF but as I could read, not so experienced, I assumed it was CF, and from the image, I sent now u can see that there are not so many requests in the timespan, and CF has 1200 per 5 min, and in my case it’s not even close.
I just don’t understand why when I put CF on pause, my response comes through. I have tested this yesterday and today.
So to conclude, you are referring to that this 429 is coming from my WPX server or this is Gateway response?
I got it now, so since I’m proxied via CF, my server does not see the original IP rather sees the CF IP request, and blocks the request, and than we can see that Origin still shows the 429, and that indicates that my server blocked the request.
I appreciate your time, please do not close this thread, I will investigate again on my server. Thanks a ton!
