My new users are suddenly getting the following error after using the refresh button to connect their patreon to access the content on a specific page;
Sorry. Login aborted due to an API error. – Patreon returned: Too many bad requests Time to cool down.
Can someone elaborate what is causing this error?
We have already tried deactivating and activating the plugin again.
This error was shown while on mobile and logged in as our creator account testing it on our own page but other users have also reported the same issue.
animeclips.online/ultra
This is due to a rate limit that gets triggered when too many bad requests are made from a single IP address. You can read more about it here. These blocks last for 30 minutes. Your site is currently making too many invalid requests to the Patreon API.
The most likely reason is that the connection between the plugin and Patreon is broken - potentially due to an expired OAuth token. To verify this, you can:
- Go to Platform | Applications | Patreon and verify that the access token for client used by your WordPress site has not expired.
- Go to the “Health Check” page in your plugin and review any logs that might be available.
You won’t be able to re-establish a new connection while the API is blocking your requests.
Here’s how to remediate the issue:
- Head to the plugin settings and clear the client ID, secret, access token, and refresh token fields under “Connection details,” then hit “Update settings”.
- Temporarily deactivate the plugin.
- Wait 60 minutes to ensure your IP is no longer blocked.
- Re-enable the plugin and go through the “Connect site” flow to re-establish the connection.
After these steps, the integration should obtain a new, valid access token.
Unfortunately that didn’t work. We only have one wordpress site connected to the IP.
The token was indeed expired so we clicked the refresh button but that didn’t seem to help.
We waited 1h+ before setting up a new connection and activating the plugin beforehand.
This page is only available to my members who decide to subscribe to a tier.
They can then login using the patreon and so on.
We still see a spike of requests from your ip at 7:10am PT which is 15 mins before your post. There haven’t been any requests since then. Can you retry the connect flow again now? Anything useful in the health check logs? You can DM you health-check logs / screenshots on what happens when you try to connect.
The site health shows that everything is good.
We tried again by deleting the api client and starting from scratch and attached will be the messages we get.
We also get the “couldn’t connect” error message whenever we try to click on update settings.
We also don’t understand why there’s many requests from the same IP (if ours) since we’re only doing request casually so something else or someone else might be triggering it?
Looks like your client in Platform | Applications | Patreon is now updated. Can you make sure that “connection details” in the WordPress plugin has the same client id / secret / access token / refresh token as in the link that I shared? The information here should be persisted and consistent even after a page reload.
Make sure not to share the access token / secret / refresh token details with anyone.
We also get the “couldn’t connect” error message whenever we try to click on update settings.
This is expected when the connection details are reset to empty fields.
We also don’t understand why there’s many requests from the same IP (if ours) since we’re only doing request casually so something else or someone else might be triggering it?
The plugin might be attempting to refresh the access token with expired credentials.
If this doesn’t work, lets move to DMs, I’ll can try help debug this further.
