• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Fixed: 12.5.30 - Backup doesnt work

No offense, but looking at the strange issues you have been reporting in the forum I guess that you are not sticking with mainstream standards in many aspects of your Linux system and Plesk installation, but are rather taking the "off-road" approach to many configurations. My impression is that you have manual installations or changes to data that are interfering with Plesk stuff. A standard Plesk 12.5.30 runs almost perfectly trouble-free on any Linux system. Have you considered to revert to a best practice approach? Maybe that will solve many of the issues? Just a simple user-to-user advice from me: Let Plesk do the job and give it the control over the system it needs. It will most likely work fine. Problems most often only exist when you leave the mainstream standard path.
 
> We have more than one machine :-D | We use many different instances - this bugs are every from different machines

All Machines are default without CLI improvements.
Sometimes - like this machine - we use the Plesk API, for some cronjobs.
In this case, it can be a bug in the new API in 12.5.x - we search on it on the other site
 
After Fix Plesk configuration after Update to Plesk 12.5.x with the command
Code:
plesk repair all -y -v
Backups works fine

I dont know, but any bug in the Plesk engine. Anyway, the above command fix the isssue
 
Back
Top