• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Unable to create the remote backup: Cannot read public key

Kaspar

API expert
Plesk Guru
I am running into an issue where all remote bakups fail with the error: Unable to create the remote backup: Cannot read public key.

This only happens with all remote backups, no matter what type of remote connection or storage I use. AWS S3, Google Drive, Dropbox and FTP all fail with this error. While using local storage works fine.

The error is a bit vague (imho). I first thought the login credentials/keys for remote strorage access didn't work. But I have tested those and they work. So I don't think that's the issue. Changing the Plesk Backups Encryption option doesn't seem to make any difference either.

I believe I have encountered this issue before, but I can't remember how I solved it. There also isn't a lot of info I could find on the subject.

Any one any suggestions?
 
Back
Top