• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • The ImunifyAV extension is now deprecated and no longer available for installation.
    Existing ImunifyAV installations will continue operating for three months, and after that will automatically be replaced with the new Imunify extension. We recommend that you manually replace any existing ImunifyAV installations with Imunify at your earliest convenience.

Issue Plesk Backup with Microsoft OneDrive Error

nunoarmada

New Pleskian
Server operating system version
Debian 10.13
Plesk version and microupdate number
Plesk Obsidian 18.0.67 Update #1 Web Pro Edition
HeY! Yesterday i connected my MS account to plesk in order to create backups remotely. I also installed MS Onedrive backup extensions and subscribed Cloud Remote PRO.
I configured my MS account on plesk but everytime i try to create a backup i have this error:

Error:
Unable to create the remote backup: Transport error: Extension transport: ext://one-drive-backup/server/: Microsoft OneDrive returns the error: Unauthenticated
Warning:
Unable to delete the incomplete remote backup. Error: Failed to exec pmm-ras: Exit code: 129: Transport error: Extension transport: ext://one-drive-backup/server: Required parameter not passed: "refresh_token"

Any help?
 
Hello, @nunoarmada . There is an exiting thread about this issue, which you may find here. To sum up, it was determined that the issue is on Microsoft's end and our engineers are still trying to catch their attention. You can review the discussion here.
 
Back
Top