I have gone through every post regarding this issue and I’ve not been able to resolve it. I have even created a blank wordpress install, the only plugin being Patreon Wordpress.
I have set up a post with the minumum gate levels. But I just can’t seem to unlock content, I end up in a loop - unlock content > Allow connection.
I just can’t get the plugin to work.
What is the error or issue that you encounter while unlocking a locked post?
The health check has over 50 logs from the last couple of days;
fetch_tiers - API v2 Class - UUID bdb76ab7-8481-41a4-be4b-75f788105e21 - Response code: 401 Response :{“errors”:[{“code”:1,“code_name”:“Unauthorized”,“detail”:“The server could not verify that you are authorized to access the URL requested. You either supplied the wrong credentials (e.g. a bad password), or your browser doesn’t understand how to supply the credentials required.”,“id”:“bdb76ab7-8481-41a4-be4b-75f788105e21”,“status”:“401”,“title”:“Unauthorized”}]}
Front end wise.
When is visit {site url}/patreon-authorization/
I am directed to the wp login screen and there is an error message -
Sorry - No authorization code received from Patreon.
Your site doesnt seem to have connection to Patreon. You can try force-refreshing it by applying the below guide:
I’ve followed those steps. Now, when trying to unlock the post I get directed to the login page with a message of;
Sorry. Logging in with Patreon is disabled in this Website. Please contact administrator.
When I select Enable Login with Patreon and try the unlock post process all over again I don’t get redirected and the post is still locked.
What am I doing wrong?
Read this thread and the other ones that are up here, but as I’m having the same problem right now, and I am on a Pro plan. I see it’s fixed in an update, but my Patrons are still caught in a loop trying to access my Wordpress content. And indeed, the connection errors in the health check show people trying to log in and not succeeding.
My wordpress site is using Your site is using:
WP 5.5.3 with PHP 7.3.23
Patreon WordPress 1.6.9 with API v2
Robert you need to go to your WP admin -> Patreon Settings -> and then enable “login with Patreon”
Yvo did you force-refresh your site’s connection to Patreon?
I can confirm I did do this but got stuck in the loop again.
Does it make a difference if I created my patreon membership using via google account?
The only way to confirm is test. Try creating a Patreon test account with a different email via normal registration and check if that will behave differently.
I have te same issue.
Old Patrons still have access, but the 3 new ones from today (including a testaccount by myself) don’t get access.
Please help!
mindgasm . net
WP 5.5.3 with PHP 7.4.13
Patreon WordPress 1.6.9 with API v2
Patron Plugin Pro 1.4.8
Patreon Button, Widgets and Plugin 2.0.9
These are the last 50 connection issues encountered by your site when contacting Patreon API. These are here for general info on health of the connection of your WP site to Patreon API. They only constitute an error if there are a lot of recent ones. Healthiest integrations should have a number of them (up to 50) in the long run.
0 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
0 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
0 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
0 days ago
delete_post_webhook - API v2 Class - UUID 163ad06b-ce89-43ee-8423-136891c741e9 - Response code: 401 Response :{“errors”:[{“code”:1,“code_name”:“Unauthorized”,“detail”:“The server could not verify that you are authorized to access the URL requested. You either supplied the wrong credentials (e.g. a bad password), or your browser doesn’t understand how to supply the credentials required.”,“id”:“163ad06b-ce89-43ee-8423-136891c741e9”,“status”:“401”,“title”:“Unauthorized”}]}
0 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
0 days ago
delete_post_webhook - API v2 Class - UUID b6dbbfaa-07d1-454d-bd22-99c0c54f868a - Response code: 401 Response :{“errors”:[{“code”:1,“code_name”:“Unauthorized”,“detail”:“The server could not verify that you are authorized to access the URL requested. You either supplied the wrong credentials (e.g. a bad password), or your browser doesn’t understand how to supply the credentials required.”,“id”:“b6dbbfaa-07d1-454d-bd22-99c0c54f868a”,“status”:“401”,“title”:“Unauthorized”}]}
0 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
0 days ago
delete_post_webhook - API v2 Class - UUID 4adf6955-2d94-4b56-a33a-9c57297d7ce7 - Response code: 401 Response :{“errors”:[{“code”:1,“code_name”:“Unauthorized”,“detail”:“The server could not verify that you are authorized to access the URL requested. You either supplied the wrong credentials (e.g. a bad password), or your browser doesn’t understand how to supply the credentials required.”,“id”:“4adf6955-2d94-4b56-a33a-9c57297d7ce7”,“status”:“401”,“title”:“Unauthorized”}]}
0 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
0 days ago
delete_post_webhook - API v2 Class - UUID d8643fab-aeb2-413e-9c4d-bcd087bd97e7 - Response code: 401 Response :{“errors”:[{“code”:1,“code_name”:“Unauthorized”,“detail”:“The server could not verify that you are authorized to access the URL requested. You either supplied the wrong credentials (e.g. a bad password), or your browser doesn’t understand how to supply the credentials required.”,“id”:“d8643fab-aeb2-413e-9c4d-bcd087bd97e7”,“status”:“401”,“title”:“Unauthorized”}]}
0 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
0 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
0 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
0 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
0 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
0 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
0 days ago
delete_post_webhook - API v2 Class - UUID 76bb730f-b49b-4d8a-b615-6f9791d37cf9 - Response code: 401 Response :{“errors”:[{“code”:1,“code_name”:“Unauthorized”,“detail”:“The server could not verify that you are authorized to access the URL requested. You either supplied the wrong credentials (e.g. a bad password), or your browser doesn’t understand how to supply the credentials required.”,“id”:“76bb730f-b49b-4d8a-b615-6f9791d37cf9”,“status”:“401”,“title”:“Unauthorized”}]}
0 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
0 days ago
delete_post_webhook - API v2 Class - UUID 45d4ee48-a540-43ed-8b38-bd9a249f31fd - Response code: 401 Response :{“errors”:[{“code”:1,“code_name”:“Unauthorized”,“detail”:“The server could not verify that you are authorized to access the URL requested. You either supplied the wrong credentials (e.g. a bad password), or your browser doesn’t understand how to supply the credentials required.”,“id”:“45d4ee48-a540-43ed-8b38-bd9a249f31fd”,“status”:“401”,“title”:“Unauthorized”}]}
0 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
0 days ago
delete_post_webhook - API v2 Class - UUID f46f1d6c-c409-44d4-baf9-721a67697c5f - Response code: 401 Response :{“errors”:[{“code”:1,“code_name”:“Unauthorized”,“detail”:“The server could not verify that you are authorized to access the URL requested. You either supplied the wrong credentials (e.g. a bad password), or your browser doesn’t understand how to supply the credentials required.”,“id”:“f46f1d6c-c409-44d4-baf9-721a67697c5f”,“status”:“401”,“title”:“Unauthorized”}]}
0 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
0 days ago
delete_post_webhook - API v2 Class - UUID ba3f7010-53a3-452a-8853-2f65d01441cc - Response code: 401 Response :{“errors”:[{“code”:1,“code_name”:“Unauthorized”,“detail”:“The server could not verify that you are authorized to access the URL requested. You either supplied the wrong credentials (e.g. a bad password), or your browser doesn’t understand how to supply the credentials required.”,“id”:“ba3f7010-53a3-452a-8853-2f65d01441cc”,“status”:“401”,“title”:“Unauthorized”}]}
0 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
0 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
0 days ago
delete_post_webhook - API v2 Class - UUID 37a01011-ab86-492e-8f99-6e1ba73351e8 - Response code: 401 Response :{“errors”:[{“code”:1,“code_name”:“Unauthorized”,“detail”:“The server could not verify that you are authorized to access the URL requested. You either supplied the wrong credentials (e.g. a bad password), or your browser doesn’t understand how to supply the credentials required.”,“id”:“37a01011-ab86-492e-8f99-6e1ba73351e8”,“status”:“401”,“title”:“Unauthorized”}]}
0 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
0 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
0 days ago
delete_post_webhook - API v2 Class - UUID 0a9fff54-0990-4312-a4c6-4f459a8e4554 - Response code: 401 Response :{“errors”:[{“code”:1,“code_name”:“Unauthorized”,“detail”:“The server could not verify that you are authorized to access the URL requested. You either supplied the wrong credentials (e.g. a bad password), or your browser doesn’t understand how to supply the credentials required.”,“id”:“0a9fff54-0990-4312-a4c6-4f459a8e4554”,“status”:“401”,“title”:“Unauthorized”}]}
0 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
0 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
0 days ago
delete_post_webhook - API v2 Class - UUID 93276808-d5a5-4817-bc22-43532b30f662 - Response code: 401 Response :{“errors”:[{“code”:1,“code_name”:“Unauthorized”,“detail”:“The server could not verify that you are authorized to access the URL requested. You either supplied the wrong credentials (e.g. a bad password), or your browser doesn’t understand how to supply the credentials required.”,“id”:“93276808-d5a5-4817-bc22-43532b30f662”,“status”:“401”,“title”:“Unauthorized”}]}
0 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
0 days ago
delete_post_webhook - API v2 Class - UUID 94ddeb9c-a476-4bd5-8c31-9676187179c0 - Response code: 401 Response :{“errors”:[{“code”:1,“code_name”:“Unauthorized”,“detail”:“The server could not verify that you are authorized to access the URL requested. You either supplied the wrong credentials (e.g. a bad password), or your browser doesn’t understand how to supply the credentials required.”,“id”:“94ddeb9c-a476-4bd5-8c31-9676187179c0”,“status”:“401”,“title”:“Unauthorized”}]}
0 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
0 days ago
delete_post_webhook - API v2 Class - UUID 0d8334c5-a208-460d-8424-99a94e6f1e27 - Response code: 401 Response :{“errors”:[{“code”:1,“code_name”:“Unauthorized”,“detail”:“The server could not verify that you are authorized to access the URL requested. You either supplied the wrong credentials (e.g. a bad password), or your browser doesn’t understand how to supply the credentials required.”,“id”:“0d8334c5-a208-460d-8424-99a94e6f1e27”,“status”:“401”,“title”:“Unauthorized”}]}
0 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
0 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
0 days ago
delete_post_webhook - API v2 Class - UUID d1108c00-ac07-4350-bd89-3d69220343ad - Response code: 401 Response :{“errors”:[{“code”:1,“code_name”:“Unauthorized”,“detail”:“The server could not verify that you are authorized to access the URL requested. You either supplied the wrong credentials (e.g. a bad password), or your browser doesn’t understand how to supply the credentials required.”,“id”:“d1108c00-ac07-4350-bd89-3d69220343ad”,“status”:“401”,“title”:“Unauthorized”}]}
0 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
0 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
0 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
0 days ago
delete_post_webhook - API v2 Class - UUID 2213ad2a-edde-4159-8fd5-2c03789f348d - Response code: 401 Response :{“errors”:[{“code”:1,“code_name”:“Unauthorized”,“detail”:“The server could not verify that you are authorized to access the URL requested. You either supplied the wrong credentials (e.g. a bad password), or your browser doesn’t understand how to supply the credentials required.”,“id”:“2213ad2a-edde-4159-8fd5-2c03789f348d”,“status”:“401”,“title”:“Unauthorized”}]}
0 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
0 days ago
delete_post_webhook - API v2 Class - UUID b5fe2fe2-bd50-4d71-8b54-bd94eb3c56eb - Response code: 401 Response :{“errors”:[{“code”:1,“code_name”:“Unauthorized”,“detail”:“The server could not verify that you are authorized to access the URL requested. You either supplied the wrong credentials (e.g. a bad password), or your browser doesn’t understand how to supply the credentials required.”,“id”:“b5fe2fe2-bd50-4d71-8b54-bd94eb3c56eb”,“status”:“401”,“title”:“Unauthorized”}]}
0 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
0 days ago
delete_post_webhook - API v2 Class - UUID e26678c8-e1b6-4422-a4ff-b35625f5839b - Response code: 401 Response :{“errors”:[{“code”:1,“code_name”:“Unauthorized”,“detail”:“The server could not verify that you are authorized to access the URL requested. You either supplied the wrong credentials (e.g. a bad password), or your browser doesn’t understand how to supply the credentials required.”,“id”:“e26678c8-e1b6-4422-a4ff-b35625f5839b”,“status”:“401”,“title”:“Unauthorized”}]}
0 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
0 days ago
delete_post_webhook - API v2 Class - UUID 6eb33a51-664c-465f-b3e9-70683ab0f48b - Response code: 401 Response :{“errors”:[{“code”:1,“code_name”:“Unauthorized”,“detail”:“The server could not verify that you are authorized to access the URL requested. You either supplied the wrong credentials (e.g. a bad password), or your browser doesn’t understand how to supply the credentials required.”,“id”:“6eb33a51-664c-465f-b3e9-70683ab0f48b”,“status”:“401”,“title”:“Unauthorized”}]}
0 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
I just noticed, that in my creator account those last 3 users don’t show under patrons/relationship manager.
I did get the “New $ patron, meet mr.xy” email for each of them though.
When I log at patreon in with my todays test-patron subscriber, it shows the membership as active.
which hints at an issue on patreons site itself, not the plugin.
Yes, since its 1st of month and payments are being processed, there may be some load at the Patreon service that may cause oddities. Also new patrons from today may not have been processed yet. You should check on this situation with those two patrons tomorrow or Thursday.
I have tried this but I’m still stuck in the loop.
Steps:
Can you DM me the link to that gated post?
I am having the exact same issue. I’m using Siteground hosting and have deactivated sg-optimizer and loginizer, and using Patreon Wordpress plugin 1.6.9 and still having the problem. I’ve disconnected the site so that users can gain access. It’s a bummer because I just launched today.
0 days ago
Response code: 401 Response :{“error”: “invalid_client”}
0 days ago
fetch_user - API v2 Class - UUID 8b7e8d8b-cb84-4840-a486-d6c683e8ee58 - Response code: 401 Response :{“errors”:[{“code”:1,“code_name”:“Unauthorized”,“detail”:“The server could not verify that you are authorized to access the URL requested. You either supplied the wrong credentials (e.g. a bad password), or your browser doesn’t understand how to supply the credentials required.”,“id”:“8b7e8d8b-cb84-4840-a486-d6c683e8ee58”,“status”:“401”,“title”:“Unauthorized”}]}
0 days ago
Response code: 401 Response :{“error”: “invalid_client”}
0 days ago
fetch_user - API v2 Class - UUID 3797cc7c-79bc-4434-9484-fdecf4575aa0 - Response code: 401 Response :{“errors”:[{“code”:1,“code_name”:“Unauthorized”,“detail”:“The server could not verify that you are authorized to access the URL requested. You either supplied the wrong credentials (e.g. a bad password), or your browser doesn’t understand how to supply the credentials required.”,“id”:“3797cc7c-79bc-4434-9484-fdecf4575aa0”,“status”:“401”,“title”:“Unauthorized”}]}
0 days ago
delete_client - API v2 Class - UUID b8e864a3-0692-4187-9581-72f07d611827 - Response code: 204 Response :
0.08 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
0.08 days ago
fetch_user - API v2 Class - UUID 51a5ad15-16fd-4772-8948-0828c9cdd480 - Response code: 401 Response :{“errors”:[{“code”:1,“code_name”:“Unauthorized”,“detail”:“The server could not verify that you are authorized to access the URL requested. You either supplied the wrong credentials (e.g. a bad password), or your browser doesn’t understand how to supply the credentials required.”,“id”:“51a5ad15-16fd-4772-8948-0828c9cdd480”,“status”:“401”,“title”:“Unauthorized”}]}
0.08 days ago
fetch_creator_info - API v2 Class - UUID 37c5d9c2-296a-48ec-bb89-93ec3d6e2f98 - Response code: 401 Response :{“errors”:[{“code”:1,“code_name”:“Unauthorized”,“detail”:“The server could not verify that you are authorized to access the URL requested. You either supplied the wrong credentials (e.g. a bad password), or your browser doesn’t understand how to supply the credentials required.”,“id”:“37c5d9c2-296a-48ec-bb89-93ec3d6e2f98”,“status”:“401”,“title”:“Unauthorized”}]}
0.27 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
0.27 days ago
get_posts - API v2 Class - UUID c6dd421a-89af-487f-b743-f8030d5365ee - Response code: 401 Response :{“errors”:[{“code”:1,“code_name”:“Unauthorized”,“detail”:“The server could not verify that you are authorized to access the URL requested. You either supplied the wrong credentials (e.g. a bad password), or your browser doesn’t understand how to supply the credentials required.”,“id”:“c6dd421a-89af-487f-b743-f8030d5365ee”,“status”:“401”,“title”:“Unauthorized”}]}
0.5 days ago
Response code: 401 Response :{“error”: “invalid_grant”}
0.5 days ago
fetch_user - API v2 Class - UUID 528d8b76-9d06-4bbf-8dcf-354c5c881738 - Response code: 401 Response :{“errors”:[{“code”:1,“code_name”:“Unauthorized”,“detail”:“The server could not verify that you are authorized to access the URL requested. You either supplied the wrong credentials (e.g. a bad password), or your browser doesn’t understand how to supply the credentials required.”,“id”:“528d8b76-9d06-4bbf-8dcf-354c5c881738”,“status”:“401”,“title”:“Unauthorized”}]}
0.5 days ago
fetch_user - API v2 Class - UUID 8251ffc2-f05a-4430-aaea-c22897ccc7ad - Response code: 401 Response :{“errors”:[{“code”:1,“code_name”:“Unauthorized”,“detail”:“The server could not verify that you are authorized to access the URL requested. You either supplied the wrong credentials (e.g. a bad password), or your browser doesn’t understand how to supply the credentials required.”,“id”:“8251ffc2-f05a-4430-aaea-c22897ccc7ad”,“status”:“401”,“title”:“Unauthorized”}]}
19.2 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5514 milliseconds
19.34 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5514 milliseconds
19.39 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5515 milliseconds
19.43 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5513 milliseconds
19.47 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5513 milliseconds
19.52 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5513 milliseconds
19.54 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5514 milliseconds
19.56 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5514 milliseconds
19.64 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5515 milliseconds
19.69 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5514 milliseconds
19.72 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5514 milliseconds
20.22 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5513 milliseconds
20.25 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5514 milliseconds
20.33 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5514 milliseconds
20.52 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5513 milliseconds
20.53 days ago
delete_post_webhook - API v2 Class - UUID 11162a11-c843-44fc-a526-d63c97886bba - Response code: 204 Response :
20.78 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5514 milliseconds
21.28 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5514 milliseconds
21.31 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5514 milliseconds
21.57 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5513 milliseconds
21.58 days ago
get_posts - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received
22.3 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5513 milliseconds
22.37 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5514 milliseconds
22.54 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5514 milliseconds
22.65 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5514 milliseconds
22.66 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5513 milliseconds
22.67 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5514 milliseconds
22.69 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5513 milliseconds
22.7 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5513 milliseconds
22.71 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5514 milliseconds
22.73 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5513 milliseconds
22.73 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5513 milliseconds
22.74 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5513 milliseconds
22.76 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5513 milliseconds
22.77 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5514 milliseconds
22.78 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5514 milliseconds
22.79 days ago
get_posts - API v2 Class - WP error message cURL error 28: Resolving timed out after 5514 milliseconds
I am having this exact issue too, people are pledging $10 and sign in to the website, it says have the subscriber role but they can’t access the content still. I disconnected and reconnected my site but it still just tells them that they need to pledge of log in with Patreon.
edit: It seems that people who have pledged before are able to access the posts but new patrons are not able to access it.
invalid_client
Your site seems to have lost connection to the api. Can you apply the steps in the below guide to refresh it?
Your issue may be 1st of month patron processing issue at Patreon side. Do they still have problems right now?
