Infinite loop after allowing authentication

Janek · March 15, 2020, 2:16am

I’m having a great time with the Patreon Wordpress plugin. Seems like everytime the wind blows the connection to the Patreon API fails and my client contacts me to fix it because their Patreons are unable to access the exclusive website content. Normally I resolve any authentication errors by refreshing the tokens on Patreon, however this time I had to delete and recreate the Patreon API. Unfortunately now I get an infinite loop where it keeps redirecting back to the locked content after allowing the API access. I’ve tried on multiple patreon accounts (thankfully some of our team are Patrons) and get the same result.

I’m using API V1, but V2 presents the same issue. I’ve tried every combination of settings, and cache clearing. In the meantime I’ve bee forced to just remove this plugin since it simply doesnt function…

Whats troubling to me is that the setup wizard doesnt even work properly, nor does the deletion of existing connections within Wordpress. Meaning I have to manually remove and recreate the API connections. I’ve read somewhere on here you have to remove the WP-OPTIONS row referring to the Patreon API version to run the setup again but honestly shouldnt have to delve into the Wordpress tables just to run the setup wizard since the whole point of the wizard is for people who are less competent to be able to set this up themselves. Fortunately I can manually do this but I cant imagine how others fair here.

Heres a screenshot example of the loop I’m experiencing:
Clicking unlock with patreon sends you to the API approval screen

Then clicking allow here just send you back to the original page with the option to unlock or refresh. both options send you back to the approval screen and so on and so forth.

codebard · March 15, 2020, 2:33am

If you attempt disconnecting/reconnecting your site to Patreon with version 1.5.1 of the plugin, it should just remove the references to apiv2 that’s in your options and it should allow you to fully transition to v2.

This, may require that you delete any existing client for that site at the api clients page:

Unfortunately the setup wizard cannot just refresh/reconnect while an old app exists for the site with the incorrect credentials. (ie, lost, expired etc).

Just try it out and let me know if it fixes your issue.

Also, last 50 connection errors in Patreon Settings -> Health check menu may be helpful to disclose.

codebard · March 15, 2020, 2:49am

Also: Do you use Wordfence?

Janek · March 15, 2020, 3:03am

I’ve scrubbed the API on API clients page about 4 times trying both V1 and V2.
We were running the latest version as well on the plugin as well.
The Patreon health check seems next to useless, everytime we’ve ever had an issue it reported “Patreon health is great” and yet the error log was reporting failures.

We use Flywheel managed hosting, Im not sure what security they use but we dont use Wordfence on our site.

## Your Patreon integration health is great!

### Last 50 connection errors

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.08 days ago**

Response code: 204 Response :

**0.08 days ago**

cURL error 28: Resolving timed out after 5514 milliseconds

**0.09 days ago**

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":"61620b16-ed56-4e15-b387-13a4f7a6490e","status":"401","title":"Unauthorized"}]}

**0.09 days ago**

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":"1ca7b1cd-d6db-4b01-838d-71e354561737","status":"401","title":"Unauthorized"}]}

**0.09 days ago**

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":"1d1ca1bb-e23c-44f1-a089-4c931be43a5d","status":"401","title":"Unauthorized"}]}

**0.09 days ago**

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":"79dbe320-4dea-4939-9f73-fed03711e2ba","status":"401","title":"Unauthorized"}]}

**0.1 days ago**

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":"73c282f5-3afd-4134-aa9d-b959ad9a1332","status":"401","title":"Unauthorized"}]}

**0.1 days ago**

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":"81faf620-fede-4aa1-a1d6-b07b4951f07d","status":"401","title":"Unauthorized"}]}

**0.13 days ago**

cURL error 28: Resolving timed out after 5513 milliseconds

**0.13 days ago**

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":"eb5324c8-c9d0-4a18-908c-a365341646e3","status":"401","title":"Unauthorized"}]}

**0.15 days ago**

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":"9e1546cc-ae7d-4244-9bcb-9ed936a059d3","status":"401","title":"Unauthorized"}]}

**0.15 days ago**

Response code: 401 Response :{"error": "invalid_grant"}

**0.15 days ago**

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":"6ed8c2ae-bd57-453d-8238-0ae3db8ae7d9","status":"401","title":"Unauthorized"}]}

**0.15 days ago**

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":"392ecadc-3a40-404a-82b1-3b956ed39d00","status":"401","title":"Unauthorized"}]}

**0.15 days ago**

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":"0ac1d554-12e6-4c24-a2f6-ccf3d7e7a237","status":"401","title":"Unauthorized"}]}

**0.15 days ago**

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":"240da1ff-6e06-4089-9cd9-622e1e6977f0","status":"401","title":"Unauthorized"}]}

**4.14 days ago**

Response code: 401 Response :{"error": "invalid_grant"}

codebard · March 15, 2020, 7:29pm

cURL error 28: Resolving timed out after 5514 milliseconds

After you resolved your app details issue, this kind of timeout happening may indicate that the host is either having connectivity issues to Patreon, or their security measures (ie mod_security or the like) are just dropping connection to Patreon.

Checking up with your host may be a good idea. Also, any other security plugin you may be using at your site may need consideration.

Within next week, 1.5.2 will go out with a feature to do short-time caching of patron info to mitigate such temporary connection issues, but if there is a setup at your host which is preventing proper connectivity to Patreon api, that must be addressed.

Janek · March 16, 2020, 9:01am

Pretty sure that error only occurred after a ran the loop 20 something times with different patreon accounts and has nothing to do with the host.

codebard · March 16, 2020, 3:10pm

Possibly. However finding out what kind of security measures which your host has may be very beneficial to determine where is this coming from.

Where were you hosted again?

BLUE_BLACK · March 17, 2020, 9:14pm

Today I got same issue in my 2 different website , both hosted in Dreamhost

codebard · March 17, 2020, 9:15pm

Can you post last 50 connection errors in Health check section under ‘Patreon Settings’?

BLUE_BLACK · March 18, 2020, 11:05am

This is https://www.sleazemovies.com Log

0.08 days ago

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”:“7783ae49-7fad-4b45-88c3-5150e7f097e2”,“status”:“401”,“title”:“Unauthorized”}]}

0.18 days ago

cURL error 28: Resolving timed out after 5513 milliseconds

0.19 days ago

cURL error 28: Resolving timed out after 5515 milliseconds

0.19 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

0.19 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

0.19 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

0.64 days ago

cURL error 28: Resolving timed out after 5515 milliseconds

0.64 days ago

cURL error 28: Resolving timed out after 5515 milliseconds

0.64 days ago

cURL error 28: Resolving timed out after 5513 milliseconds

0.64 days ago

cURL error 28: Resolving timed out after 5515 milliseconds

0.64 days ago

cURL error 28: Resolving timed out after 5516 milliseconds

0.64 days ago

cURL error 28: Resolving timed out after 5520 milliseconds

3.18 days ago

Response code: 400 Response :{“error”: “invalid_request”, “error_description”: “Mismatching redirect URI.”}

3.18 days ago

Response code: 400 Response :{“error”: “invalid_request”, “error_description”: “Mismatching redirect URI.”}

3.63 days ago

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”:“8502a33b-c73f-4245-9604-d1d40cbee63e”,“status”:“401”,“title”:“Unauthorized”}]}

3.63 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

3.63 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

3.63 days ago

cURL error 28: Resolving timed out after 5518 milliseconds

3.63 days ago

cURL error 28: Resolving timed out after 5515 milliseconds

3.64 days ago

cURL error 28: Resolving timed out after 5515 milliseconds

3.64 days ago

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”:“76eba253-96f8-4d10-b789-d042a473bd75”,“status”:“401”,“title”:“Unauthorized”}]}

3.64 days ago

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”:“f83057a1-df0c-41af-bdcb-f667e56012ba”,“status”:“401”,“title”:“Unauthorized”}]}

3.64 days ago

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”:“a3658d68-0c76-485d-b839-7e50684f9f41”,“status”:“401”,“title”:“Unauthorized”}]}

3.64 days ago

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”:“84c651ce-416f-4d8e-9e9a-ab8ff911898c”,“status”:“401”,“title”:“Unauthorized”}]}

3.64 days ago

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”:“8e8056ed-1bc2-48ad-95e1-65c5ac920fe9”,“status”:“401”,“title”:“Unauthorized”}]}

3.64 days ago

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”:“dbf01b58-955a-4be7-a9d9-09291e95e995”,“status”:“401”,“title”:“Unauthorized”}]}

3.64 days ago

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”:“3eec3cfa-b6be-40e4-9fd7-6eb2ca4c83cd”,“status”:“401”,“title”:“Unauthorized”}]}

3.64 days ago

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”:“67e340b6-60f7-4457-87c3-4f265b66d27f”,“status”:“401”,“title”:“Unauthorized”}]}

3.64 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

3.64 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

3.64 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

3.65 days ago

cURL error 28: Resolving timed out after 5515 milliseconds

3.65 days ago

cURL error 28: Resolving timed out after 5515 milliseconds

3.65 days ago

cURL error 28: Resolving timed out after 5513 milliseconds

3.65 days ago

cURL error 28: Resolving timed out after 5518 milliseconds

3.66 days ago

cURL error 28: Resolving timed out after 5518 milliseconds

3.67 days ago

cURL error 28: Resolving timed out after 5515 milliseconds

3.67 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

3.68 days ago

cURL error 28: Resolving timed out after 5512 milliseconds

3.68 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

3.7 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

3.7 days ago

cURL error 28: Resolving timed out after 5515 milliseconds

3.7 days ago

cURL error 28: Resolving timed out after 5515 milliseconds

3.71 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

14.61 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

14.61 days ago

cURL error 28: Resolving timed out after 5513 milliseconds

14.61 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

19.15 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

21.57 days ago

cURL error 28: Resolving timed out after 5536 milliseconds

22.14 days ago

cURL error 28: Resolving timed out after 5520 milliseconds

BLUE_BLACK · March 18, 2020, 11:06am

This is https://www.eroti.ga/ Log

0.19 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

0.62 days ago

cURL error 28: Resolving timed out after 5513 milliseconds

11 days ago

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

12.28 days ago

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

12.28 days ago

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”:“d17a6005-b80d-4911-89e7-8158faf1d0d4”,“status”:“401”,“title”:“Unauthorized”}]}

12.88 days ago

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

12.88 days ago

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”:“c2a84c96-69b5-4598-b595-fe03897051f7”,“status”:“401”,“title”:“Unauthorized”}]}

12.88 days ago

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

12.88 days ago

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”:“9c4fdcdb-d350-4984-9e53-e0cb7399887a”,“status”:“401”,“title”:“Unauthorized”}]}

12.88 days ago

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

12.88 days ago

Response code: 204 Response :

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

12.88 days ago

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

BLUE_BLACK · March 18, 2020, 11:08am

Both websites hosted by Dreamhost + CloudFlare and no any plugins as Wordfence , etc…
This issue started yesterday

codebard · March 18, 2020, 4:41pm

Have you updated or changed your Patreon WordPress in that period?

Are you using Patron Pro?

Janek · March 18, 2020, 9:41pm

I can confirm that Patron Pro doesn’t make a difference in my case. I tried both with and without. I can also confirm that the plugin was updated before all this loop started to happen.

BLUE_BLACK · March 19, 2020, 2:31am

I don’t use pro !
I didn’t update it before start this issue

codebard · March 19, 2020, 8:25pm

Blue, can you post your last 50 connection errors again? The latest state i mean - as of today.

BLUE_BLACK · March 19, 2020, 8:53pm

Fresh Log of https://www.sleazemovies.com

0.9 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

0.91 days ago

cURL error 28: Resolving timed out after 5516 milliseconds

1.01 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

1.01 days ago

cURL error 28: Resolving timed out after 5518 milliseconds

1.01 days ago

cURL error 28: Resolving timed out after 5515 milliseconds

1.01 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

1.01 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

1.01 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

1.03 days ago

cURL error 28: Resolving timed out after 5513 milliseconds

1.03 days ago

cURL error 28: Resolving timed out after 5513 milliseconds

1.03 days ago

cURL error 28: Resolving timed out after 5513 milliseconds

1.03 days ago

cURL error 28: Resolving timed out after 5517 milliseconds

1.03 days ago

cURL error 28: Resolving timed out after 5515 milliseconds

1.07 days ago

cURL error 28: Resolving timed out after 5517 milliseconds

1.08 days ago

cURL error 28: Resolving timed out after 5516 milliseconds

1.08 days ago

cURL error 28: Resolving timed out after 5519 milliseconds

1.49 days ago

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”:“7783ae49-7fad-4b45-88c3-5150e7f097e2”,“status”:“401”,“title”:“Unauthorized”}]}

1.59 days ago

cURL error 28: Resolving timed out after 5513 milliseconds

1.59 days ago

cURL error 28: Resolving timed out after 5515 milliseconds

1.6 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

1.6 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

1.6 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

2.05 days ago

cURL error 28: Resolving timed out after 5515 milliseconds

2.05 days ago

cURL error 28: Resolving timed out after 5515 milliseconds

2.05 days ago

cURL error 28: Resolving timed out after 5513 milliseconds

2.05 days ago

cURL error 28: Resolving timed out after 5515 milliseconds

2.05 days ago

cURL error 28: Resolving timed out after 5516 milliseconds

2.05 days ago

cURL error 28: Resolving timed out after 5520 milliseconds

4.59 days ago

Response code: 400 Response :{“error”: “invalid_request”, “error_description”: “Mismatching redirect URI.”}

4.59 days ago

Response code: 400 Response :{“error”: “invalid_request”, “error_description”: “Mismatching redirect URI.”}

5.04 days ago

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”:“8502a33b-c73f-4245-9604-d1d40cbee63e”,“status”:“401”,“title”:“Unauthorized”}]}

5.04 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

5.04 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

5.04 days ago

cURL error 28: Resolving timed out after 5518 milliseconds

5.04 days ago

cURL error 28: Resolving timed out after 5515 milliseconds

5.05 days ago

cURL error 28: Resolving timed out after 5515 milliseconds

5.05 days ago

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”:“76eba253-96f8-4d10-b789-d042a473bd75”,“status”:“401”,“title”:“Unauthorized”}]}

5.05 days ago

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”:“f83057a1-df0c-41af-bdcb-f667e56012ba”,“status”:“401”,“title”:“Unauthorized”}]}

5.05 days ago

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”:“a3658d68-0c76-485d-b839-7e50684f9f41”,“status”:“401”,“title”:“Unauthorized”}]}

5.05 days ago

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”:“84c651ce-416f-4d8e-9e9a-ab8ff911898c”,“status”:“401”,“title”:“Unauthorized”}]}

5.05 days ago

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”:“8e8056ed-1bc2-48ad-95e1-65c5ac920fe9”,“status”:“401”,“title”:“Unauthorized”}]}

5.05 days ago

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”:“dbf01b58-955a-4be7-a9d9-09291e95e995”,“status”:“401”,“title”:“Unauthorized”}]}

5.05 days ago

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”:“3eec3cfa-b6be-40e4-9fd7-6eb2ca4c83cd”,“status”:“401”,“title”:“Unauthorized”}]}

5.05 days ago

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”:“67e340b6-60f7-4457-87c3-4f265b66d27f”,“status”:“401”,“title”:“Unauthorized”}]}

5.05 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

5.05 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

5.05 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

5.05 days ago

cURL error 28: Resolving timed out after 5515 milliseconds

5.05 days ago

cURL error 28: Resolving timed out after 5515 milliseconds

5.06 days ago

cURL error 28: Resolving timed out after 5513 milliseconds

BLUE_BLACK · March 19, 2020, 8:54pm

0.89 days ago

cURL error 28: Resolving timed out after 5515 milliseconds

0.89 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

0.92 days ago

cURL error 28: Resolving timed out after 5513 milliseconds

0.92 days ago

cURL error 28: Resolving timed out after 5518 milliseconds

0.92 days ago

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”:“418e4c37-94b7-44b9-9cad-14f9629c6ba9”,“status”:“401”,“title”:“Unauthorized”}]}

0.92 days ago

cURL error 28: Resolving timed out after 5518 milliseconds

0.92 days ago

cURL error 28: Resolving timed out after 5515 milliseconds

0.92 days ago

cURL error 28: Resolving timed out after 5517 milliseconds

0.92 days ago

cURL error 28: Resolving timed out after 5522 milliseconds

0.92 days ago

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”:“b9850d01-7895-4910-9a29-031d865d9b2e”,“status”:“401”,“title”:“Unauthorized”}]}

0.92 days ago

cURL error 28: Resolving timed out after 5518 milliseconds

0.92 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

1.6 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

2.02 days ago

cURL error 28: Resolving timed out after 5513 milliseconds

12.41 days ago

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

13.69 days ago

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

13.69 days ago

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”:“d17a6005-b80d-4911-89e7-8158faf1d0d4”,“status”:“401”,“title”:“Unauthorized”}]}

14.29 days ago

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

14.29 days ago

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”:“c2a84c96-69b5-4598-b595-fe03897051f7”,“status”:“401”,“title”:“Unauthorized”}]}

14.29 days ago

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

14.29 days ago

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”:“9c4fdcdb-d350-4984-9e53-e0cb7399887a”,“status”:“401”,“title”:“Unauthorized”}]}

14.29 days ago

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

14.29 days ago

Response code: 204 Response :

14.29 days ago

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

14.29 days ago

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

14.29 days ago

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

14.29 days ago

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

14.29 days ago

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

14.29 days ago

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

14.29 days ago

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

14.29 days ago

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

14.29 days ago

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

14.29 days ago

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

14.29 days ago

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

14.29 days ago

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

14.29 days ago

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

14.29 days ago

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

14.29 days ago

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

14.29 days ago

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

14.29 days ago

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

14.29 days ago

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

14.29 days ago

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

14.29 days ago

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

14.29 days ago

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

14.29 days ago

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

14.29 days ago

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

14.29 days ago

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

14.29 days ago

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

14.29 days ago

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

14.29 days ago

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

codebard · March 19, 2020, 9:49pm

Blue, there are way too many timeouts happening when resolving Patreon’s api address.

This means that your web host’s server is not reliably resolving Patreon’s api address. Therefore it is not able to contact Patreon API, leading to timeout errors. For your site to be able to access the api, it must be able to resolve www.patreon.com and api.patreon.com domains easily.

Can you post a support ticket at your host with the above information, and also include the logs which you just posted?

BLUE_BLACK · March 20, 2020, 4:21am

OK Thanks My Friend…

Topic		Replies	Views
Users Not Able To Connect Wordpress Plugin	79	2120	December 7, 2020
WP Patreon Login, Sync, & Setup Wizard not working Wordpress Plugin	12	644	January 26, 2022
401 Error he server could not verify that you are authorized to access the URL requested API Feedback	2	2951	February 21, 2020
Looping login issue Wordpress Plugin	17	1379	May 12, 2021
Patreon Locking Stopped working: 401 Response :{"error": "invalid_grant"} Wordpress Plugin	17	613	May 1, 2023

Infinite loop after allowing authentication

Related Topics