Please help ASAP! Patrons can't sign in to read paywalled WP posts

I’ve got the Patreon plugin installed on my WP site and have paywalled some posts. But it looks like people can’t sign in to read them.

Linking to WP is the only reason our community joined Patreon. If we can’t get this to work, we have no reason to be on Patreon.

If I click on “Unlock with Patreon,” it takes me to a page that asks you to make a custom pledge, which is ridiculous. I want the posts visible to people who are patrons in my standard tiers. What is this custom pledge thing? This will be very confusing for new people who are trying to sign up as members of our community - they’ve been told about the standard tiers, they won’t know what to do with a custom pledge page!

Below “Unlock” it also says, “Already a qualifying Patreon member? Refresh to access this content.” The word “Refresh” links to a login page. But when I complete the login, I still can’t access the posts!

Other users who are my patrons are reporting exactly the same problems, so it’s not just me.

This is time sensitive because our next newsletter is supposed to go out tomorrow. Quick help would be very much appreciated!

Can you see your custom tiers when you are locking posts? In ‘Patreon Level’ metabox in post editor?

Yes. One of the options is to make posts visible to “any patron.” That’s what I selected.

Can you try setting a post to a higher tier and see if this affects anything?

The only change is now the paywall message specifies the level at which you have to join, and when it takes you to the custom pledge page, it sets the default dollar amount to that amount.

But I still can’t get past the actual paywall, which is the real problem!

Thanks for any help you can give; I appreciate it.

If I’m already signed into Patreon when I click “Refresh,” instead of taking me to a login screen, it takes me to a page saying “[Username] would like to . . . view your public profile/view your email address.” If I click “allow” it takes me back to the WP post, but the paywall is still up.

If I’m not already signed into Patreon when I click “Refresh,” it takes me to a login screen. When I log in, it takes me back to the WP post, but the paywall is still up.

Thanks for your help!

Do you have any caching plugin at your site? Do you use cloudflare?

And its not a custom pledge page that you are seeing with the tiers - its the pledge flow. Its expected. Are you not able to pledge at that screen? Are you using your original creator account to test? That wouldnt work.

No Cloudflare. I don’t think we have any caching plugins on our site - I’ll admit that I’m not an expert, though. We’re a pretty simple operation.

Thanks for any further help you can provide!

Are you using your creator account to test?

I had several other people try it on their own machines, and they’re all getting the same results. But I did sign out from all my accounts before trying it, just to make sure that wasn’t affecting it.

Can you first use the below guide to force refresh your site’s connection to Patreon.

And then check if your host has opcache or other server side caching. Also you can DM me a screenshot of your plugins in plugin manager.

OK, I did the force-refresh and it did not produce any change in the problem.

I just sent you a message here in the forums with screenshots showing all my plugins.

Thanks for your help - very grateful!

Basically you are the one who has this persistent issue. I cant think of anything but a situation with either your hosting - opcache etc - or a plugin at your site modifying behavior. Your main issue is that when the user is returned to your site from Patreon after pledge flow, the content doesnt get unlocked. This can happen due to caching plugins, server side caching, cookie issues at your site, anything that modifies login, security plugins at your site or security measures at your host.

Try seeing if any error is reported in Patreon Settings → Health Check menu and c/p them here.

Additionally you may contact your host and ask them whether they are blocking Cloudflare IPs and also ask them Patreon IPs are reachable.

I appreciate your help.

I’m not seeing anything called “health check” under settings for my creator page in Patreon, settings for user profile in Patreon, or settings for the plugin in WP. Where should I be looking?

Will call the host tomorrow.

We already have a plan in motion to eventually switch from our current website to a simpler one with fewer moving parts; perhaps we’ll accelerate that plan and see if the new site doesn’t have this issue.

Thanks!

I found it! Looks like there were a few errors yesterday when we were working on all this. Possibly when I did the force-refresh because at first I tried running the auto-reinstall after only deleting the Patreon app for this site, and that didn’t work, so I deleted the Patreon apps for all my sites and re-ran the auto-reinstall.

Thank you for your help - I’m grateful! Here’s a copy/paste of the error list:

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.83 days ago

create_refresh_client - API v2 Class - UUID ae695314-79ad-402b-ae32-954cc84022cd - Response code: 400 Response :{“errors”:[{“code”:null,“code_name”:“DuplicateEntity”,“detail”:“Existing client for user and parent client”,“id”:“ae695314-79ad-402b-ae32-954cc84022cd”,“status”:“400”,“title”:“Duplicate entity”}]}

0.83 days ago

fetch_creator_info - API v2 Class - UUID 62f3d793-3d7a-4cc0-926f-edb523d8320a - 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”:“62f3d793-3d7a-4cc0-926f-edb523d8320a”,“status”:“401”,“title”:“Unauthorized”}]}

47.9 days ago

fetch_creator_info - API v2 Class - UUID 4c9820d2-3393-45f8-bd0f-789fda671ce7 - 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”:“4c9820d2-3393-45f8-bd0f-789fda671ce7”,“status”:“401”,“title”:“Unauthorized”}]}

47.9 days ago

Response code: 401 Response :{“error”: “invalid_grant”}

47.9 days ago

fetch_creator_info - API v2 Class - UUID c6fb6697-9e4b-4a76-91e3-67917e2fa10d - 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”:“c6fb6697-9e4b-4a76-91e3-67917e2fa10d”,“status”:“401”,“title”:“Unauthorized”}]}

47.9 days ago

Response code: 401 Response :{“error”: “invalid_grant”}

47.9 days ago

fetch_creator_info - API v2 Class - UUID 854b3ef9-a765-40ab-8404-bf190643e53f - 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”:“854b3ef9-a765-40ab-8404-bf190643e53f”,“status”:“401”,“title”:“Unauthorized”}]}

47.9 days ago

Response code: 401 Response :{“error”: “invalid_grant”}

47.9 days ago

fetch_creator_info - API v2 Class - UUID 8846fde3-2e4a-42ea-877a-c61ca3ebc07b - 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”:“8846fde3-2e4a-42ea-877a-c61ca3ebc07b”,“status”:“401”,“title”:“Unauthorized”}]}

47.9 days ago

fetch_tiers - API v2 Class - UUID 60bc4cab-665a-4708-8548-ff0ff2c02b96 - 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”:“60bc4cab-665a-4708-8548-ff0ff2c02b96”,“status”:“401”,“title”:“Unauthorized”}]}

47.9 days ago

Response code: 401 Response :{“error”: “invalid_grant”}

47.9 days ago

fetch_creator_info - API v2 Class - UUID b20f6e17-96d5-4880-9bf6-ed1ef753756c - 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”:“b20f6e17-96d5-4880-9bf6-ed1ef753756c”,“status”:“401”,“title”:“Unauthorized”}]}

47.9 days ago

Response code: 401 Response :{“error”: “invalid_grant”}

47.9 days ago

fetch_creator_info - API v2 Class - UUID 4280b2a9-8adf-400f-806d-e8857a89ca82 - 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”:“4280b2a9-8adf-400f-806d-e8857a89ca82”,“status”:“401”,“title”:“Unauthorized”}]}

47.9 days ago

Response code: 401 Response :{“error”: “invalid_grant”}

47.9 days ago

fetch_creator_info - API v2 Class - UUID 48ac772c-33bf-4b6a-b323-efe4bbd1de53 - 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”:“48ac772c-33bf-4b6a-b323-efe4bbd1de53”,“status”:“401”,“title”:“Unauthorized”}]}

47.9 days ago

Response code: 401 Response :{“error”: “invalid_grant”}

47.9 days ago

fetch_creator_info - API v2 Class - UUID 64ba44ae-9ade-4875-8ad6-398f8b8d931f - 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”:“64ba44ae-9ade-4875-8ad6-398f8b8d931f”,“status”:“401”,“title”:“Unauthorized”}]}

47.9 days ago

fetch_tiers - API v2 Class - UUID 59e35368-2b32-475f-8b51-5ca57e9d94cd - 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”:“59e35368-2b32-475f-8b51-5ca57e9d94cd”,“status”:“401”,“title”:“Unauthorized”}]}

47.9 days ago

Response code: 401 Response :{“error”: “invalid_grant”}

47.9 days ago

fetch_creator_info - API v2 Class - UUID 10b11451-dec8-48cb-b67d-af2d219ee7cf - 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”:“10b11451-dec8-48cb-b67d-af2d219ee7cf”,“status”:“401”,“title”:“Unauthorized”}]}

47.9 days ago

Response code: 401 Response :{“error”: “invalid_grant”}

47.9 days ago

fetch_creator_info - API v2 Class - UUID 7d2951f7-9f87-4dd1-a303-8b1aff90e3e0 - 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”:“7d2951f7-9f87-4dd1-a303-8b1aff90e3e0”,“status”:“401”,“title”:“Unauthorized”}]}

47.9 days ago

Response code: 401 Response :{“error”: “invalid_grant”}

47.9 days ago

fetch_creator_info - API v2 Class - UUID 293fc4d2-f48e-449c-b07f-e6bbad2f7ab7 - 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”:“293fc4d2-f48e-449c-b07f-e6bbad2f7ab7”,“status”:“401”,“title”:“Unauthorized”}]}

47.9 days ago

Response code: 401 Response :{“error”: “invalid_grant”}

47.9 days ago

fetch_creator_info - API v2 Class - UUID f7817629-e5ad-425f-b57a-ca3df01d7b38 - 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”:“f7817629-e5ad-425f-b57a-ca3df01d7b38”,“status”:“401”,“title”:“Unauthorized”}]}

47.9 days ago

fetch_tiers - API v2 Class - UUID 67c6beba-581d-4251-bdaa-e43dc65b342a - 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”:“67c6beba-581d-4251-bdaa-e43dc65b342a”,“status”:“401”,“title”:“Unauthorized”}]}

47.9 days ago

Response code: 401 Response :{“error”: “invalid_grant”}

47.9 days ago

fetch_creator_info - API v2 Class - UUID 4e33508d-c784-4982-b806-cf118edeaa3c - 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”:“4e33508d-c784-4982-b806-cf118edeaa3c”,“status”:“401”,“title”:“Unauthorized”}]}

47.9 days ago

Response code: 401 Response :{“error”: “invalid_grant”}

47.9 days ago

fetch_creator_info - API v2 Class - UUID 94ff8935-3fe9-4e7b-89da-9510229d18e6 - 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”:“94ff8935-3fe9-4e7b-89da-9510229d18e6”,“status”:“401”,“title”:“Unauthorized”}]}

47.9 days ago

fetch_tiers - API v2 Class - UUID eeb58e95-68ea-4259-ad11-6fdcae44f1ab - 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”:“eeb58e95-68ea-4259-ad11-6fdcae44f1ab”,“status”:“401”,“title”:“Unauthorized”}]}

47.9 days ago

Response code: 401 Response :{“error”: “invalid_grant”}

47.9 days ago

fetch_creator_info - API v2 Class - UUID b5277642-54e6-4f70-a4f6-0aa748acb321 - 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”:“b5277642-54e6-4f70-a4f6-0aa748acb321”,“status”:“401”,“title”:“Unauthorized”}]}

47.9 days ago

Response code: 401 Response :{“error”: “invalid_grant”}

47.9 days ago

fetch_creator_info - API v2 Class - UUID 24215ff3-7630-4006-88fd-914ed06c99b9 - 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”:“24215ff3-7630-4006-88fd-914ed06c99b9”,“status”:“401”,“title”:“Unauthorized”}]}

47.9 days ago

Response code: 401 Response :{“error”: “invalid_grant”}

47.9 days ago

fetch_creator_info - API v2 Class - UUID 61664593-9104-4e63-8397-1821a39bb640 - 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”:“61664593-9104-4e63-8397-1821a39bb640”,“status”:“401”,“title”:“Unauthorized”}]}

47.9 days ago

Response code: 401 Response :{“error”: “invalid_grant”}

47.9 days ago

fetch_creator_info - API v2 Class - UUID ccfc2667-2c07-49b8-918b-270fe643fe1f - 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”:“ccfc2667-2c07-49b8-918b-270fe643fe1f”,“status”:“401”,“title”:“Unauthorized”}]}

47.9 days ago

fetch_tiers - API v2 Class - UUID ddc784b8-32fb-42ec-952d-b668c7857d19 - 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”:“ddc784b8-32fb-42ec-952d-b668c7857d19”,“status”:“401”,“title”:“Unauthorized”}]}

47.9 days ago

Response code: 401 Response :{“error”: “invalid_grant”}

47.9 days ago

fetch_creator_info - API v2 Class - UUID 00494e7e-f97a-47f3-87fc-2174d61c4e5a - 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”:“00494e7e-f97a-47f3-87fc-2174d61c4e5a”,“status”:“401”,“title”:“Unauthorized”}]}

47.9 days ago

Response code: 401 Response :{“error”: “invalid_grant”}

47.9 days ago

fetch_creator_info - API v2 Class - UUID d94e532a-6625-47c9-811e-ce136b7c5999 - 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”:“d94e532a-6625-47c9-811e-ce136b7c5999”,“status”:“401”,“title”:“Unauthorized”}]}

47.9 days ago

Response code: 401 Response :{“error”: “invalid_grant”}

47.9 days ago

fetch_creator_info - API v2 Class - UUID 5638a4ae-0336-4114-9863-6ab29d85ac78 - 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”:“5638a4ae-0336-4114-9863-6ab29d85ac78”,“status”:“401”,“title”:“Unauthorized”}]}

47.9 days ago

Response code: 401 Response :{“error”: “invalid_grant”}

It doesnt seem like you successfully reconnected your site to the api.

Have you connected another Wordpress site to the api before? If so, you will have to manually create an app for this site and c/p its details to plugin settings.

I did successfully connect it, after the failed attempt that produced that error message, per my previous message: “At first I tried running the auto-reinstall after only deleting the Patreon app for this site, and that didn’t work, so I deleted the Patreon apps for all my sites and re-ran the auto-reinstall.”

I know the process for manually connecting additional sites after the first one, which is why I had multiple apps. I deleted all those apps so I could quickly reconnect my main site, per my previous message: “so I deleted the Patreon apps for all my sites and re-ran the auto-reinstall.”

Thanks for your help with this! Unless you have any additional suggestions, it looks like the problem is in my website and I don’t have the tech-savvy to find it. We have already been planning to launch a new, much simpler site (one that I can maintain myself, even with my low level of tech-savvy), so at this point my plan is to simply accelerate the launch of the new site and hope that we don’t encounter any difficulties connecting Patreon to the new site.

Yep, definitely at this point the site or the hosting are potential sources which could easily cause such issues.

Doing a simple experiment by acquiring a very simple, cheap hosting account at a place like Godaddy or Bluehost (something like $4 month etc), setting up a fresh WP site on a new subdomain there and installing the Patreon plugins first can allow you to start from a good base. Then you could start re-installing your plugins one by one. If the connection breaks at any point, then you have found the culprit.

Then again it may be a config issue which stems from some setting that remained in your db from a plugin from ages ago. Such situations are rare but happens to long-standing sites at times. Starting from a fresh slate could eliminate such issues as well.