Error Validation for transport “xxxxxx” failed: Could not create path directory “/xxxx”: Token refresh failed at /usr/local/cpanel/3rdparty/perl/532

[AlexSot]

Hi, I keep on getting this error after about 7days from creation of additional destination backup on google drive.

I follow this procedure to setup everything How to Configure Google Drive as a Backup Additional Destination - cPanel Knowledge Base - cPanel Documentation

I also followed this thread Google Validation for Transport Error , but I have no IPv6 in all points mentioned.

Everything works well, however every time, after about 7 days , the transport is not validated and I need to recreate everything.
Can you please advice how to solve?

 

[cPDavidL]

Hello, Alex!

Might I suggest checking this article: Google Drive backup validation failure: "Could not create path directory"

The error and behavior you describe is most often associated with rate limitations within the Google API token settings. Can you please confirm what value is set there?

 

[AlexSot]

Hi, thanks for the replay.

The actual error is this:
Error: Validation for transport “XXXXXX” failed: Could not create path directory “/XXXXX”: Token refresh failed at /usr/local/cpanel/3rdparty/perl/532/lib/perl5/cpanel_lib/OAuth/Cmdline.pm line 83

It's a bit different than the one you mentioned. I however checked the values and they are set to Queries per day 1,000,000,000; Queries per 100 seconds per user 10,000 and Queries per 100 seconds to 10,000.

 

[cPDavidL]

The 'Token refresh failed' error means that the application is unable to acquire a new authentication token from the remote system(Google's API). This most often is due to reaching certain quotas.

Queries per day 1,000,000,000; Queries per 100 seconds per user 10,000 and Queries per 100 seconds to 10,000.

Per the documentation from google regarding their API, The quota 'requests per 100 seconds per user', has a maximum value of 1000. You may try setting it at that threshold, to see if the transport is able to function with that level.

Something that stands out to me is your comment:

after about 7 days , the transport is not validated and I need to recreate everything

Do I infer correctly that before recreation, attempting to validate the destination by the panel is failing as well?

 

[AlexSot]

Per the documentation from google regarding their API, The quota 'requests per 100 seconds per user', has a maximum value of 1000. You may try setting it at that threshold, to see if the transport is able to function with that level.

These values where there by default. I amended to 1000, however I still get the same error when validating from WHM.

Do I infer correctly that before recreation, attempting to validate the destination by the panel is failing as well?

Yes.
Basically after I set up the Google Drive API and create account credentials, I configure the Google Drive transport from WHM and it validates. For about 7 days everything works... BKs are sent to my google drive with no problems. After I usually receive an email from VPS stating that transport had failed with that error. If from WHM I try to validate, it will give me that same error. What I usually do then is to delete everything and start again the procedure, which will allow me again 7 days of backups transportation till it fails again.

 

[cPRex]

That's definitely frustrating that it only works for 7 days, as intermittent issues are always the worst. However, consistently working for 7 days does seem to indicate an issue with some connection reaching a limit. Are there any errors on the Google side of things that you can see, as we know the configuration on the cPanel side of things isn't being changed.

 

[AlexSot]

It is indeed!
I continued researching once I could not see any error from google and arrived to this page which might give an answer to why this happens every 7days

Using OAuth 2.0 to Access Google APIs | Authorization | Google for Developers

developers.google.com

 

[AlexSot]

It is indeed!
I continued researching once I could not see any error from google and arrived to this page which might give an answer to why this happens every 7days

Using OAuth 2.0 to Access Google APIs | Authorization | Google for Developers

developers.google.com

This Still did not solve the problem....
I Changed the status from "Testing" to "Production", the verification status is "Verification not required", but I still get the same error after 7 days.
Token refresh failed at /usr/local/cpanel/3rdparty/perl/532/lib/perl5/cpanel_lib/OAuth/Cmdline.pm line 83

Is it possible that I'm the only one with this error????

 

[cPRex]

Is it possible that I'm the only one with this error????

It's always possible - feel free to open a ticket with our team and we can do some additional homework on this.

 

[BWSLLC]

This Still did not solve the problem....
I Changed the status from "Testing" to "Production", the verification status is "Verification not required", but I still get the same error after 7 days.
Token refresh failed at /usr/local/cpanel/3rdparty/perl/532/lib/perl5/cpanel_lib/OAuth/Cmdline.pm line 83

Is it possible that I'm the only one with this error????

I have this same issue so don't feel alone! Did you ever solve this one or open a ticket with the cpanel team? I have gone through everything save the last step suggested(OAuth 2.0) without luck as well.

I assumed the 7 day issue was due to backup frequency/retention on the web server. E.g. once it goes to save a second weekly backup, it is having issues removing the old backup. Not proven but that is my initial thought on it.

 

[hmaddy]

i am also faced the same issue and solved with a cpanel update.

 

[vicos]

2023 and the problem still persists:

Token refresh failed at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/OAuth/Cmdline.pm line 84

I even generated a new client secret in Google API console and no change.

 

[cPRex]

@vicos - I don't see that a ticket was created by any of the previous posters, so feel free to reach out to us to get more details.