• 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.

Forwarded to devs Backup status incorrectly reported on home screen

carini

Basic Pleskian
Username:

TITLE

Backup status incorrectly reported on home screen

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk Obsidian v18.0.63_build1800240902.09 os_Ubuntu 20.04

PROBLEM DESCRIPTION

On home screen a running backup is incorrectly show as finished, but in reality is still running, not succeeded nor failed



STEPS TO REPRODUCE

Start a backup, go to home screen

ACTUAL RESULT

Running backup is not clearly shown as running

EXPECTED RESULT

Running backups should be shown as "running" or "in progress"

ANY ADDITIONAL INFORMATION

(DID NOT ANSWER QUESTION)

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Thank you for bringing the issue to our attention. We were able to reproduce the behavior on our end and the same is identified as a bug with ID PPPM-14639. We will introduce a fix in one of the upcoming Plesk releases. Unfortunately, I cannot provide any ETA at the time being. You may observe our change log here.
 
Back
Top