Content not unlocking for some users

Wordpress Plugin
1

Hello,

I’ve been using the plugin for over a year and have found it very useful - so first of all, thank you.

I have, however, had a persistent issue with about 20% of new Patreon subscribers not being able to view the locked content. From what I can gather, in most cases the content become visible after 2-24 hours, which sounds like the “first of the month” issue. However, this happens with relative frequency throughout the month.

I’ve disabled all caching, and don’t believe I’m using any plugins that would be a conflict. I’ve also force reconnected to Patreon, and triple checked the connection details. Can you recommend further steps I can take to solve this issue? Should I install the debug package or is that outdated? Every time I get a New Patreon Supporter notification, it’s difficult to get excited, knowing that I may get an email in 30 minutes from someone frustrated that they’re unable to access what they just paid for.

Thanks in advance for you help!

Info about the site:
WP 5.8.2 with PHP 7.4.27
Patreon WordPress 1.8.0 with API v2
Siteground Hosting

Here are the latest error logs:

1.36 days ago

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

1.36 days ago

fetch_user - API v2 Class - UUID 6425d0a5-d742-4150-8c58-f068bed8e20b - 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”:“6425d0a5-d742-4150-8c58-f068bed8e20b”,“status”:“401”,“title”:“Unauthorized”}]}

4.1 days ago

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

4.1 days ago

fetch_user - API v2 Class - UUID e9eb4431-f86c-4fcb-b5af-694362dbad39 - 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”:“e9eb4431-f86c-4fcb-b5af-694362dbad39”,“status”:“401”,“title”:“Unauthorized”}]}

4.1 days ago

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

4.1 days ago

fetch_user - API v2 Class - UUID a98cf328-2af9-459f-b95b-d38c9b16969f - 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”:“a98cf328-2af9-459f-b95b-d38c9b16969f”,“status”:“401”,“title”:“Unauthorized”}]}

4.15 days ago

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

4.15 days ago

fetch_user - API v2 Class - UUID 99d62def-2244-4b54-8a91-ad198a88c6c4 - 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”:“99d62def-2244-4b54-8a91-ad198a88c6c4”,“status”:“401”,“title”:“Unauthorized”}]}

4.15 days ago

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

4.15 days ago

fetch_user - API v2 Class - UUID aa3763eb-ba37-4d75-b44b-3b72e455f2d7 - 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”:“aa3763eb-ba37-4d75-b44b-3b72e455f2d7”,“status”:“401”,“title”:“Unauthorized”}]}

4.15 days ago

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

4.15 days ago

fetch_user - API v2 Class - UUID f4edfec5-33bc-48d9-9647-1cc29081267d - 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”:“f4edfec5-33bc-48d9-9647-1cc29081267d”,“status”:“401”,“title”:“Unauthorized”}]}

4.15 days ago

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

4.15 days ago

fetch_user - API v2 Class - UUID 637cef6b-6654-4229-95db-5956f776910c - 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”:“637cef6b-6654-4229-95db-5956f776910c”,“status”:“401”,“title”:“Unauthorized”}]}

4.47 days ago

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

4.47 days ago

fetch_user - API v2 Class - UUID 256e63df-156e-481e-a640-1cab2f830663 - 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”:“256e63df-156e-481e-a640-1cab2f830663”,“status”:“401”,“title”:“Unauthorized”}]}

4.6 days ago

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

4.6 days ago

fetch_user - API v2 Class - UUID 06bf5daf-6b5d-439c-b81f-ccffc1de0b75 - 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”:“06bf5daf-6b5d-439c-b81f-ccffc1de0b75”,“status”:“401”,“title”:“Unauthorized”}]}

4.6 days ago

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

4.6 days ago

fetch_user - API v2 Class - UUID 9ee706e7-1dd7-4170-9ebf-7a1ddfa76a8f - 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”:“9ee706e7-1dd7-4170-9ebf-7a1ddfa76a8f”,“status”:“401”,“title”:“Unauthorized”}]}

4.6 days ago

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

4.6 days ago

fetch_user - API v2 Class - UUID 92584412-bc37-409e-823b-696953fe85e0 - 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”:“92584412-bc37-409e-823b-696953fe85e0”,“status”:“401”,“title”:“Unauthorized”}]}

4.6 days ago

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

4.6 days ago

fetch_user - API v2 Class - UUID 6a3854b1-bdfe-4991-b27d-d5f343d76a78 - 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”:“6a3854b1-bdfe-4991-b27d-d5f343d76a78”,“status”:“401”,“title”:“Unauthorized”}]}

4.67 days ago

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

4.67 days ago

fetch_user - API v2 Class - UUID 25d88929-c65f-4014-ba5d-d9b6c67b901c - 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”:“25d88929-c65f-4014-ba5d-d9b6c67b901c”,“status”:“401”,“title”:“Unauthorized”}]}

4.67 days ago

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

4.67 days ago

fetch_user - API v2 Class - UUID 70f30132-c21a-4236-bb2f-4daa10b7f0c3 - 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”:“70f30132-c21a-4236-bb2f-4daa10b7f0c3”,“status”:“401”,“title”:“Unauthorized”}]}

4.67 days ago

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

4.67 days ago

fetch_user - API v2 Class - UUID 8fa237f9-b4ed-4f9c-8820-123992c80562 - 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”:“8fa237f9-b4ed-4f9c-8820-123992c80562”,“status”:“401”,“title”:“Unauthorized”}]}

4.81 days ago

fetch_user - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received

4.82 days ago

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

4.82 days ago

fetch_user - API v2 Class - UUID 9f3ebde2-9f2c-403f-89e7-d418593b031d - 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”:“9f3ebde2-9f2c-403f-89e7-d418593b031d”,“status”:“401”,“title”:“Unauthorized”}]}

4.82 days ago

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

4.82 days ago

fetch_user - API v2 Class - UUID 705840ab-af02-4a60-86f1-636091026301 - 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”:“705840ab-af02-4a60-86f1-636091026301”,“status”:“401”,“title”:“Unauthorized”}]}

5.09 days ago

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

5.09 days ago

fetch_user - API v2 Class - UUID de3f4ef9-66ff-4baa-b7bc-0e12f3fd5743 - 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”:“de3f4ef9-66ff-4baa-b7bc-0e12f3fd5743”,“status”:“401”,“title”:“Unauthorized”}]}

5.1 days ago

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

5.1 days ago

fetch_user - API v2 Class - UUID a3b8f8ac-8b98-4039-9258-510ed604106c - 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”:“a3b8f8ac-8b98-4039-9258-510ed604106c”,“status”:“401”,“title”:“Unauthorized”}]}

5.1 days ago

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

5.1 days ago

fetch_user - API v2 Class - UUID 477091a3-f3b3-4696-9d14-c9fb79c0dd93 - 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”:“477091a3-f3b3-4696-9d14-c9fb79c0dd93”,“status”:“401”,“title”:“Unauthorized”}]}

5.22 days ago

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

5.22 days ago

fetch_user - API v2 Class - UUID 3ce3cbce-3f41-4770-8ffd-193169ba683f - 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”:“3ce3cbce-3f41-4770-8ffd-193169ba683f”,“status”:“401”,“title”:“Unauthorized”}]}

5.22 days ago

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

5.22 days ago

fetch_user - API v2 Class - UUID f92350ea-2671-4707-8821-f6e4689cade2 - 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”:“f92350ea-2671-4707-8821-f6e4689cade2”,“status”:“401”,“title”:“Unauthorized”}]}

5.22 days ago

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

5.22 days ago

fetch_user - API v2 Class - UUID da1687c0-f227-4eb5-842d-eb048614f571 - 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”:“da1687c0-f227-4eb5-842d-eb048614f571”,“status”:“401”,“title”:“Unauthorized”}]}

5.22 days ago

fetch_user - API v2 Class - UUID - Response code: 502 Response :

Error 502

Ray ID: 6c54f5bc928129dc • 2021-12-29 18:06:01 UTC

Bad gateway

You

Browser

Working

Chicago

Cloudflare

Working

Host

Error

What happened?

The web server reported a bad gateway error.

What can I do?

Please try again in a few minutes.

Cloudflare Ray ID: 6c54f5bc928129dc • Your IP: 35.206.93.153 • Performance & security by Cloudflare

5.22 days ago

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

5.22 days ago

fetch_user - API v2 Class - UUID 946bf9c4-1872-4237-a6fd-c051f2c112e5 - 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”:“946bf9c4-1872-4237-a6fd-c051f2c112e5”,“status”:“401”,“title”:“Unauthorized”}]}

2

There seems to be various info that are not necessarily related. First of all, bad gateway that happens on your server is something that your host needs to look at.

Second, there seems to be authorization issues while patrons are trying to log in. Its difficult to determine the cause just through the messages since the cause of the issue may be due to many factors. First confirming with your host that any server side caching exists on your server or not would be good. These can range from many things, from proxy caches to opcache or Redis/memcached. Where you are hosted, your plan etc also may be important so if you can post that info that could help.

3

Got it. That’s actually the first time I’ve seen the Bad Gateway error. However the fetch_user seems to be a regular occurrence and the time seems to coincide with subscribers having authorization problems.

2.43 days ago

fetch_user - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received

I contacted the host (Siteground) and they double checked to be sure there is no server side caching happening.

For hosting, I’m using the GoGeek hosting plan listed here: WordPress Hosting - Fast and Secure Managed by Experts - SiteGround. Note, I’m not using the Cloudflare CDN. Let the know what other info I can provide you and I’d be happy to post it.

Thank you for your help!

4

The timeout is important. Did you see it again? Contacting Siteground with that specific info may be helpful. There may not be caching, but if any Cloudflare IP is filtered by Siteground backend for whatsoever reason at any point, this may cause issues.

5

Thank you for your help! I did find there was one cache setting turned on (NGINX Direct Delivery) so I also disabled that and gave it the month to see how things would function.

Interestingly, at this point I don’t get any more errors in the health check, but I’m still having the same issue with some new Patrons. I spoke to Siteground support, who double checked and assured me all caching has been disabled for the site. Cloudflare has never been enabled for the site, but I’ll contact them again and ask about the filtering.

Forgive me being a little out of my wheelhouse, but can you clarify for me what I should ask Siteground Support? If Cloudflare is turned off, is there a reason why it would still be having an effect on the site?

I’m assuming this is ultimately some problem with Siteground, but getting past the customer service-level help and getting the right person to look in the right place seems like it’ll be my challenge.

Again, thankful for your help and for the plugin!

6

Does the content not unblock for some users in the middle of the month (like right now), or does this happen for 1-2 days after the 1st of the month?

Regarding Cloudflare - I didn’t mean to turn off Cloudflare for your site (though it may have effect depending on your settings) but Siteground not filtering/blocking Cloudflare IPs. You may ask them whether they do that if you wish.

At this point collecting information on patrons who have this problem would help. The more info you collect and the more common points are there among the patrons who have this issue, the easier it is to solve it.