Issue Using Dropbox backup extension - one domain has a backup error

[David Borrink]

Server operating system version

CentOS 7.9

Plesk version and microupdate number

18.0.70 #3

I've been successfully backing up my server to Dropbox everyday for several months. Recently I'm getting daily messages involving one of the several domains I have on my server. This message comes as a warning email from my server. Does anyone have any experience with this kind of an error and what I might need to do to resolve it?

"The following errors occurred during the scheduled backup process:

Transport error: Extension transport: ext://dropbox-backup/subscription/5/: Error in call to API function "files/get_metadata": Invalid authorization value in HTTP header/URL parameter"

 

[Sebahat.hadzhi]

The error suggests there is an authorization issue. Could you please double-check the Dropbox credentials and ensure they are correct?

 

[David Borrink]

I looked in my Dropbox folders on Dropbox and I see that all my domains have backed up except for this one domain. That's what my error is for, it's for an authorization value that is invalid for just that one. This is a domain I only use for email, not for a web site.

All my other domains are backing up fine. I'm not seeing where each domain is connected with Dropbox. It's been a while. Under Backup Manager > Remote Storage Settings > Dropbox Backup I have no individual domains for settings. It's a setting for my server. There aren't individual domains with settings that I would check.

In the Websites and Domains > Backup and Restore > I choose the domain in question and I have a list of daily error messages just for this one domain. Checking any other domains looks fine. The log errors say...

Warning:
Unable get the amount of free space from the remote storage. Error: Error in call to API function "users/get_current_account": Invalid authorization value in HTTP header/URL parameter
Warning:
Unable to create the remote backup: Transport error: Extension transport: ext://dropbox-backup/subscription/5/: Error in call to API function "files/upload_session/start": Invalid authorization value in HTTP header "Authorization": "Bearer". Expecting "Bearer <oauth2-access-token>".
Warning:
Unable to delete the incomplete remote backup. Error: Failed to exec pmm-ras: Exit code: 129: Transport error: Extension transport: ext://dropbox-backup/subscription/5: Error in call to API function "files/get_metadata": Invalid authorization value in HTTP header/URL parameter

How would I check the credentials for just this one domain? I'm not seeing anything for that.

 

[trialotto]

I looked in my Dropbox folders on Dropbox and I see that all my domains have backed up except for this one domain. That's what my error is for, it's for an authorization value that is invalid for just that one. This is a domain I only use for email, not for a web site.
....

@David Borrink

I think that you should explicitly set the remote storage settings for the "mail domain" under Websites and Domains > Backup and Restore > Settings.

Please create a specific (sub-)directory on Dropbox first and use that (sub-)directory in the remote storage settings.

Afterwards, just make a backup in order to test whether the remote backup can be made (and also check Dropbox for presence of the backup).

If the backup process again results in errors, then consult the logs again.

It can be the case that the Dropbox (sub-)directory contains a backup and that the logs exhibit errors : this means that the backup can be made, but not properly - in other words, there is some unknown issue, but that issue is not likely to be a connectivity / authorization issue.

It can also be the case that the Dropbox (sub-)directory is empty : first check for connectivity / authorization issues by uploading a test file manually to the relevant Dropbox (sub-)directory - if that fails, the connectivity / authorization issue is on the Dropbox side.

It can also be the case that the that the Dropbox (sub-)directory is empty and that the logs exhibit errors : if you were able to upload a test file manually, then is almost certain that the connectivity / authorization issue is in the client side, i.e. on the Plesk side.

Please try in the chronological order mentioned above ....... and provide some feedback, if necessary.

Kind regards....