Wordpress users stuck in authorization loop

Issue:
Users attempt to unlock posts on Wordpress with their Patreon account.

Users are taken to patreon authorization as expected

Clicking Allow brings user back to locked article

Expected result:
User should see unlocked article.

Steps to fix:
if user instead hits DENY, navigates back to the site, and attempts login again, user is successful.

This leads me to believe it is a caching issue. Site uses WPRocket, and now CloudFlare.
This issue happened last year, resulting in rules set in WPRocket to never cache anything related to patreon. This worked until webhost moved us to CloudFlare for CDN. As site is a GoDaddy hosted Wordpress, I can’t change server caching rules.
I have added caching rules for patreon to our htaccess, and now that we are on CloudFlare, I have added caching rules for patreon to CloudFlare. Still the issue persists, and has been for several weeks now.

Plugin settings appear to be correct, everything matches the patreon portal.

What else can I do? I’ve searched the threads and have tried to follow any results, but none have seemed to work for our situation here.

The next thing I would like to do is disconnect the site from the patreon Wordpress plugin, and set it up again to see if that fixes anything, but I am worried that I would have to go back and manually change the authorization for the couple thousand articles on the site that each use different tiers of access. If that is how it works, that is not feasible. However if it retains the tier access settings for each article, that is something I could pursue.

So, what should I do next? I’m exhausted.

Thank you in advance for any guidance.

Yes, looks like it. What we can do to help you here is limited as both of those (wp rocket and cf) are pretty featured things and a different configuration somewhere can change everything. (disconnecting/reconnecting the site from Patreon wouldnt fix that btw).

You could move all your patron-only articles into a specific category, make the permalinks have the category in the permalink, and then add rules to wp rocket and cf to totally exclude any url that includes that category string in the path from any caching. That could work if you could do it. The other option is to move to a more compatible host somewhere.