I’m getting this, suddenly, after working fine for a long time: [image] No recent changes. I just clicked ‘retry’ while the forum was 100% up and nada, just +1’d the error.

Thanks! :slight_smile: Updated. However, strange, nothing is actually happening when I try: Placeit | Create Amazing Mockups, Logos, Videos & Designs Get Unlimited Downloads Across 150K+ Templates! Create & Customize Logos, Videos, Mockups, Flyers, Business Cards in Seconds With Placeit! I ensured popup blockers are off, but even then, it’d show something in console. I wonder if Patreon’s API is wonky? I’m going to scroll up to see where to check logs and return. Ok found logs via forum.{mySite}.com/logs: …nada, after clicking resume: [image] Seems like Patreon didn’t even attempt anything. Aside from the general button, I also tried the same individual test from recordit [image] Just nada in logs O_O To add: Placeit | Create Amazing Mockups, Logos, Videos & Designs Get Unlimited Downloads Across 150K+ Templates! Create & Customize Logos, Videos, Mockups, Flyers, Business Cards in Seconds With Placeit! Even going back to the deprecated ones that do send a response (perhaps your new ones forgot to send a success code back?), I’m getting 200 per … yet Patreon keeps saying error when I resume, which makes no sense. Even the 200 (deprecated hooks) callbacks still show nothing in logs. Is there some default filter that blocks Patreon tests in logs?

[image] vinothkannans: triggers “members:pledge:create”, “members:pledge:update” and “members:pledge:delete” No, you should only use “members:pledge:create” instead of “members:create” like I mentioned in above. [image] dylanh724: Is there some default filter that blocks Patreon tests in logs? No. [image] dylanh724: I’m getting 200 per … yet Patreon keeps saying error when I resume, which makes no sense. I think you should delete the whole webhook endpoint in the Patreon site and re-add it.

[image] vinothkannans: members:pledge:create Deleted the hook >> remade >> swapped hook secret >> members:pledge:create >> test has no response code (unlike the deprecated ones that have 200 response). Placeit | Create Amazing Mockups, Logos, Videos & Designs Get Unlimited Downloads Across 150K+ Templates! Create & Customize Logos, Videos, Mockups, Flyers, Business Cards in Seconds With Placeit! No mention of it not working yet, but I believe that takes a few hours.

Related: I had a tester donate and couldn’t get him linked. Not sure if it’s the webhook or not, but I discovered that existing users with 2FA cannot link “associated accounts” (Patreon) for whatever reason (bug?). There is also an undocumented mention that accounts are linked by matching emails - but this tester’s email is separate from Patreon, causing issues. If you’re reading this, testing a fix, heads up.

To follow up, I’m not getting an errors on the webhooks. Seems … fixed? Maybe? I have no testers, atm. However, I’m still feeling uneasy because there’s no return code (eg, 200): Clicking the test button appears to do nothing (but simply has no return code). Does the new version not return any http code?

@dylanh724 can you please try the v2 webhooks again after upgrading the plugin? Also, I converted the whole plugin to support Patreon’s v2 API in beta branch. It’s not stable yet. If possible then you can test it and let me know the feedback. For that, you have to use v2 API credentials.

Sure, I’ll give it a shot soon. Before the upgrade, just a follow-up summary that you may already know leading up to now: It worked, but showed it not working. Users were being sync’d up into the Patreon group successfully. Likely because a 200 success code was not returned, Testing the hooks would result in nothing. After a day or 2, Patreon would email you saying that your hooks are broken. ^ I think this was a false positive since it would sync just fine, just not return a code. However, a false positive may have disabled the hooks completely after a couple days. I can’t tell you if it still works or not (the testers area already sync’d). Users with 2FA (existing users that did not register via the Patreon button) experienced syncing issues since they could not link their account, if email mismatched. For some reason, “Associated Accounts” section poofs when 2FA is enabled. Existing users with 2FA that had a mismatching email would never get a Patreon sync. This is common to have different emails on forum than Patreon (especially if using +alias or forwarding).

I understand and hope it won’t happen again. And I will check the possible solution for 2FA.

[image] vinothkannans: @dylanh724 can you please try the v2 webhooks again after upgrading the plugin? Hmm, no dice: [image] [image] [image] [image] Still no 200 code~ unless the new hooks changed how they show it vs the deprecated hooks? Still feels like a return code issue.

Thanks for the test. I pushed a few more fixes and it is working fine now. [image]

Webhook Paused - Failed Request - Worked before

Product Support

dylanh724 (dh) May 5, 2020, 3:08am 45

Hmm, no dice:

Still no 200 code~ unless the new hooks changed how they show it vs the deprecated hooks? Still feels like a return code issue.

Topic		Replies	Views
Patreon webhooks failing Product Support patreon	6	1699	November 23, 2021
Patreon syncing by connection Product Support patreon	26	1739	December 27, 2022
Patreon Plugin Not Updating Product Support	20	2950	December 20, 2017
Webhook certificate verify failed Product Support patreon	2	3383	September 5, 2018
Error while trying to authorize your account with Patreon Feature patreon	2	745	November 12, 2025

Webhook Paused - Failed Request - Worked before

Related topics