Search results

Changing to ftpMaxTlsVersion = 12 did not help, i still get the same error.

I'll test as well.

Well, i do not have a license purchased from Plesk and Hetzner, where i purchased it, does not provide support for it. What can i do now?

Debian 10 is already taking more than a year, though ...

The spam the failed backups are sending every day are going on my nerves. Backup and Restore worked fine before that patch, please fix this!

Mh, where could i get help for this issue? I got my licenses via my server hoster.

I'd be also interested in more information, new servers to deploy and do not wanna use old OS. Given it doesn't even support Debian 10 yet, it seems Plesk has become inacceptably slow with keeping up.

Issue still present, noone has a idea?

It just suddenly stopped working at the first scheduled backup after that patch, had this running perfectly for years before.

I just sent a e-mail via my webmail and yes, it also occurs there.

Definately a plesk issue. Also using a hetzner box like Rar9, btw. Please fix soon.

Thanks for moving! Any idea?

Unfortunately not, the first workaround did not help, as there is no second key and the second one didn't change anything either. I just noticed i posted in the wrong forums, i'm using Obsidian, not Onyx. Can this be moved?

I got the same issues since the update.

Getting an error from mxtoolbox regarding body hash, it sees a different hash than it expects. I just activated this feature for the first time. What could be wrong?

Same here.

Haha, thank you very much! Congratulations to France!

Yes. I found the solution that does also apply to the latest Plesk Onyx and not only to 12.5: Unable to select wildcard certificate for subdomain that is installed under main domain But i'm asking myself where this inconsistency comes from. For testing i created a new domain and added...

Hello, now that the creation of wildcard certs worked, i wanted to secure my subdomains with it. The documentation says: This, unfortunatley, fails on step 4 as the wildcard certificate is not listed in the dropdown menu of subdomains but only on the main domain.

Found the issue. There were still configs in the old cli.ini of the extension itself.