Infinite loop after allowing authentication

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.

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.

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?

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

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

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

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”}

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

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

Are you using Patron Pro?

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.

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

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

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

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”}

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?

OK Thanks My Friend…

No any issue with my hosting !

Thanks for waiting. Definitely no issues here. I ran network configs anyway to make sure everything’s working as intended. I pinged both subdomains from our servers and results came up fine:

root@ps606385:~# ping api.patreon.com
PING api.patreon.com (104.16.6.49) 56(84) bytes of data.
64 bytes from 104.16.6.49: icmp_seq=1 ttl=57 time=0.737 ms
64 bytes from 104.16.6.49: icmp_seq=2 ttl=57 time=0.638 ms
64 bytes from 104.16.6.49: icmp_seq=3 ttl=57 time=0.693 ms
api.patreon.com ping statistics —
3 packets transmitted, 3 received, 0% packet loss, time 2004ms
rtt min/avg/max/mdev = 0.638/0.689/0.737/0.045 ms
.

root@ps606385:~# ping www.patreon.com
PING www.patreon.com (104.16.6.49) 56(84) bytes of data.
64 bytes from 104.16.6.49: icmp_seq=1 ttl=57 time=0.659 ms
64 bytes from 104.16.6.49: icmp_seq=2 ttl=57 time=0.665 ms
64 bytes from 104.16.6.49: icmp_seq=3 ttl=57 time=0.647 ms
^C
www.patreon.com ping statistics —
3 packets transmitted, 3 received, 0% packet loss, time 2022ms
rtt min/avg/max/mdev = 0.647/0.657/0.665/0.007 ms

Great, thanks. Can you post the last 50 connection errors log as it is now at this moment to compare with the rest?

It’s looks like now settled

1.79 days ago

cURL error 28: Resolving timed out after 5515 milliseconds

1.79 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

1.82 days ago

cURL error 28: Resolving timed out after 5513 milliseconds

1.82 days ago

cURL error 28: Resolving timed out after 5518 milliseconds

1.82 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”}]}

1.82 days ago

cURL error 28: Resolving timed out after 5518 milliseconds

1.82 days ago

cURL error 28: Resolving timed out after 5515 milliseconds

1.82 days ago

cURL error 28: Resolving timed out after 5517 milliseconds

1.82 days ago

cURL error 28: Resolving timed out after 5522 milliseconds

1.82 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”}]}

1.82 days ago

cURL error 28: Resolving timed out after 5518 milliseconds

1.82 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

2.49 days ago

cURL error 28: Resolving timed out after 5514 milliseconds

2.92 days ago

cURL error 28: Resolving timed out after 5513 milliseconds

13.31 days ago

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

14.58 days ago

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

14.58 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”}]}

15.18 days ago

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

15.18 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”}]}

15.18 days ago

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

15.18 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”}]}

15.18 days ago

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

15.18 days ago

Response code: 204 Response :

15.18 days ago

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

15.18 days ago

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

15.18 days ago

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

15.18 days ago

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

15.18 days ago

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

15.18 days ago

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

15.18 days ago

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

15.18 days ago

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

15.18 days ago

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

15.18 days ago

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

15.18 days ago

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

15.18 days ago

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

15.18 days ago

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

15.18 days ago

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

15.18 days ago

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

15.18 days ago

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

15.18 days ago

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

15.18 days ago

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

15.18 days ago

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

15.18 days ago

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

15.18 days ago

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

15.18 days ago

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

15.18 days ago

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

15.18 days ago

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

15.18 days ago

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

15.18 days ago

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

15.18 days ago

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

Yeah, last timeout seems to be from 1.79 days ago.

But still, you can occasionally try unlocking a $1 locked page with a new Patron account you created (different email) and see if you encounter any issues in the coming weeks…