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

Issue Task manager faliture

PeopleInside

Regular Pleskian
Server operating system version
Ubuntu 22.04.3 LTS
Plesk version and microupdate number
18.0.58 Update #2
Hi, today going on the Task Manager I found 4 errors related to a Plesk Domain
1706879278002.png
Should I just ignore or there are some actions I can take to cancel this error?
Thanks
 
Hard to tell with that little information. Can you ssee more by trying to click the down arrow?
 
Did you check whether the domain object 17 actually exists in the corresponding psa.domains table?
 
Thanks, as the support is not free and I have not a paid support plan and cannot pay for now, I just looked for help here.
Well I share my issue experience, hope someone else can maybe report this issues to Plesk and a fix can come with a future update.
Will be nice if the Plesk Diagnostic tool will be bale to discover and fix this issues in the future.

Thanks for your try to help :)
 
Do you know that Plesk Support is free for the first 30 days? Don't let that stop you from contacting them.

And yes, it puzzles me why the diagnostics tool didn't detect this issue as it should have.
 
And yes, it puzzles me why the diagnostics tool didn't detect this issue as it should have.
I guess that some event was defined that refers to a domain that no longer exists, or maybe a static ID is used. Indeed it would be good if someone from support could check it directly on the server.
 
Back
Top