I didn’t change any code at all but this issue just started happening randomly. I tried to fix it but I’m not receiving any requests from Patreon. I even created a separate webhook endpoint that simply logs whenever it receives any request, ignoring the content entirely, but the server doesn’t log anything as if Patreon isn’t sending anything.
I haven’t changed anything about my server hosting or code so I’m at a loss here.
My main goal is to have a webhook triggered automatically when someone subscribes to a paid tier and to send another webhook when that user cancels their subscription. If there is an easier way to do this through some integration I’m unaware of, please let me know.
I’m seeing this too, also with no code changes (although I did change some WAF rules…)
I notice that when sending test events, the failed count ticks up too.
@Chat_Rewards What HTTP status code does your webhook return? We return 204, wondering if you do the same. It might be that Patreon is not considering the 204 a success, and instead it wants a 200.
@tgvashworth both 200 and 204s are considered valid responses. I would suggest looking into your WAF logs and reviewing the settings that were changed.
Are you able to make http calls to your webhook endpoints?
I’m 90% sure it’s not the WAF because I can see the requests coming through fine and the test hooks work, even though Patreon registers them as failures. The WAF change and the hook failures were not coincident in time either.
I can make requests fine to the endpoints, yes.
@noertap Apologies, it is the WAF. It’s not blocking your test events so that looked fine to me, but it is blocking real events.
1 Like
@tgvashworth thanks for the update! Out of curiosity - did you see the test requests to get through or assumed that they get through because the test page didn’t show any errors? I find it interesting that the test request would’ve gotten through, but real ones wouldn’t. Also, we are currently working on a fix to show the exact status code of the remote endpoint in the “send test” flow. I tested the fix with one of your apis and saw a 403 being returned.
The change that shows response status_code of the remote webhook endpoint in the webhook “send test” flow just shipped. Hopefully this helps developers in the future when debugging issues with their hooks.
It keeps saying 403. I am still unsure what to do, as I’ve checked all my rules, Cloudflare settings, and nginx config. And I cannot for the life of me figure out why Patreon is still receiving 403.
