Google Backup Validation Errors
After my server updated to v70.0.34, I stated to receive Backup transport errors:
Navigating to WHM Home "Backup "Backup Configuration I tired to edit the backup and refresh the secret code (via google API), however, the box to do so was grayed out. Unable to get anywhere I deleted that backup and tried to add a new one. Now when I add the new backup, I receive the following error during validation:
Also, via google when the popup appears I get the following error:
Where do I go from here?
Unable to send "/backup/2018-05-11/accounts/site1.tar.gz" to destination "host"
Unable to send "/backup/2018-05-11/accounts/site2.tar.gz" to destination "host"
Unable to send "/backup/2018-05-11/accounts/.master.meta" to destination "host"
Unable to prune transport "host"
Unable to remove outdated backup: Token refresh failed at /usr/local/cpanel/3rdparty/perl/526/lib64/perl5/cpanel_lib/OAuth/Cmdline.pm line 83Navigating to WHM Home "Backup "Backup Configuration I tired to edit the backup and refresh the secret code (via google API), however, the box to do so was grayed out. Unable to get anywhere I deleted that backup and tried to add a new one. Now when I add the new backup, I receive the following error during validation:
Error: Validation for transport "host" failed: Could not create path directory "/host/": Cache file /var/cpanel/backups/928365448683-24uh684o1h4s1h7citb6fn65vp9ca7bc.apps.googleusercontent.com.yml not found. See GETTING STARTED in the docs for how to get started. at /usr/local/cpanel/3rdparty/perl/526/lib64/perl5/cpanel_lib/OAuth/Cmdline.pm line 191Also, via google when the popup appears I get the following error:
Google returned with the following error: 500 Can't connect to accounts.google.com:443 (No route to host) - Can't connect to accounts.google.com:443 (No route to host)
LWP::Protocol::https::Socket: connect: No route to host at /usr/local/cpanel/3rdparty/perl/526/lib64/perl5/cpanel_lib/LWP/Protocol/http.pm line 46.
Where do I go from here?
-
Hi @Dezdan If you recreate the destination do you continue to get the same error? My Google Drive backup destination isn't experiencing this issue but I did find that I could create a separate one and it was successfully validated. In case you need the knowledgebase article on how to set this up again it's located here: Google Drive - cPanel Knowledge Base - cPanel Documentation Thanks! 0 -
Hi @cPanelLauren Yes, even in recreating the destination I am still receiving the same errors. I deleted the backup configuration on my server, and then I went to the Google API and deleted the credentials specific to the backup. I started all over, creating new Google API credentials and then creating a new backup destination on my server and are still receiving the following errors. When I click Generate Credentials to generate the credentials file and the new tab appears that allows me to authorize access to my Google Drive data, I get the following error after I click the Allow button: Google returned with the following error: 500 Can't connect to accounts.google.com:443 (No route to host) - Can't connect to accounts.google.com:443 (No route to host) LWP::Protocol::https::Socket: connect: No route to host at /usr/local/cpanel/3rdparty/perl/526/lib64/perl5/cpanel_lib/LWP/Protocol/http.pm line 46.
And then on WHM Home "Backup "Backup Configuration, I receive:Error: Validation for transport "Host" failed: Could not create path directory "/host/": Cache file /var/cpanel/backups/928365448683-9sp9kkv2972sbotq0fbvucq4rm5f3k9v.apps.googleusercontent.com.yml not found. See GETTING STARTED in the docs for how to get started. at /usr/local/cpanel/3rdparty/perl/526/lib64/perl5/cpanel_lib/OAuth/Cmdline.pm line 191
Additionally, even when I created the new backup destination and new API, I see the following before I validate: 520270 -
Hi @Dezdan In that final screenshot it shows that maybe the credentials already exist (for the old google backup destination) They're stored in /var/cpanel/backups/ you might want to remove any references to them there first then recreate. I do feel like this is more to do with being unable to reach google though. I assume this was set up prior to updating, are you by chance using IPv6 at all on the server? Thanks! 0 -
Hey @cPanelLauren, In that final screenshot it shows that maybe the credentials already exist (for the old google backup destination) They're stored in /var/cpanel/backups/ you might want to remove any references to them there first then recreate.
No change.I do feel like this is more to do with being unable to reach google though. I assume this was set up prior to updating, are you by chance using IPv6 at all on the server?
No IPv6, and it was working fine prior to the most recent update. For background, you had helped me last month with an IPv6 issue: Currently: 520830 -
Thanks for the help. My Support Request ID is: 9560881 0 -
Thanks @Dezdan I'll update again once I have more information 0 -
Sadly, the my support ticket has been of no help thus far. The first individual to help told me there was no issues and I was just doing it wrong. The second individual confirmed there was an issue, then told me that a common issue is IPv6 and I should disable it; then provided a link to my own previous topic on this help forum. 0 -
HI @Dezdan I'm sorry to hear that, we're having one of our L2 analysts take another look at the ticket right now, he should be in contact with you soon. Thanks! 0 -
Thank you @cPanelLauren! That was a weird one, IPv6 would not disable! Final cure to disable IPv6: Add: net.ipv6.conf.all.disable_ipv6 = 1 To: /etc/sysctl.conf Run: sysctl -p Reboot to confirm. 0 -
Hi @Dezdan I'm really happy to hear that we were able to help get it sorted. All is working with the backup transport now then, right? Thanks! 0
Please sign in to leave a comment.
Comments
11 comments