• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Can not find domain by id error

sysunknown

New Pleskian
Server operating system version
Ubuntu 20.04.6 LTS
Plesk version and microupdate number
Plesk Obsidian Web Pro Edition Version 18.0.53 Update #2
Hey folks! How are you?
For sometime now i keep getting this error that can not find the id on Plesk logs on all my Plesk installations. I can not seem to figure out why and how to remove it. Screenshot attached and please tell me if you need more information. Thanks!
 

Attachments

  • Screenshot from 2023-07-04 10-05-22.png
    Screenshot from 2023-07-04 10-05-22.png
    70.8 KB · Views: 15
The cause can be manifold. One cause can be orphaned entries in the longtasks and longtaskparams tables. Do you have such?
# plesk db -e "SELECT * FROM longtasks;"
# plesk db -e "SELECT * FROM longtaskparams;"
In that case you could try clearing them:
# plesk db -e "DELETE FROM longtasks;"
# plesk db -e "DELETE FROM longtaskparams;"

Could you please first check this and let us know the result?
 
The cause can be manifold. One cause can be orphaned entries in the longtasks and longtaskparams tables. Do you have such?
# plesk db -e "SELECT * FROM longtasks;"
# plesk db -e "SELECT * FROM longtaskparams;"
In that case you could try clearing them:
# plesk db -e "DELETE FROM longtasks;"
# plesk db -e "DELETE FROM longtaskparams;"

Could you please first check this and let us know the result?
I do have a lot of entries when i type the two commands. I cleared them and ill check if the errors reapear and report back.
Thank you for your support.
 
The other causes are way more complicated and need a careful look at the situation on the server. I cannot recommend trying to solve them via forum help. Instead, I suggest to involve Plesk support, because they can check the issue directly on your server and either provide step-by-step solutions that match exactly the situation they find on your server or fix it right away.

To sign-in to support please go to https://support.plesk.com

If you experience login issues, please see this KB article:
https://support.plesk.com/hc/en-us/...rt-plesk-com-and-password-reset-does-not-work

If you bought your license from a reseller, your reseller should provide support for you. If the reseller does not provide support, here is an alternative:
https://support.plesk.com/hc/en-us/articles/12388090147095-How-to-get-support-directly-from-Plesk-
 
The other causes are way more complicated and need a careful look at the situation on the server. I cannot recommend trying to solve them via forum help. Instead, I suggest to involve Plesk support, because they can check the issue directly on your server and either provide step-by-step solutions that match exactly the situation they find on your server or fix it right away.

To sign-in to support please go to https://support.plesk.com

If you experience login issues, please see this KB article:
https://support.plesk.com/hc/en-us/...rt-plesk-com-and-password-reset-does-not-work

If you bought your license from a reseller, your reseller should provide support for you. If the reseller does not provide support, here is an alternative:
https://support.plesk.com/hc/en-us/articles/12388090147095-How-to-get-support-directly-from-Plesk-
I will contact plesk support but maybe another piece of info that might make this less complicated. Basically this domains that can not be found are deleted domains and it seems that some leftover configs are still on the server which i can figure out where. My Plesk server are up and running and i do not have any problems on active websites.
 
The leftovers are in the SQLite WP Toolkit database, but the solution can be complicated to a point where it is better that Plesk staff does it as else it could create more problems than it solves.
 
Hi,

I also have this problem, and in fact all 4 of my Plesk servers now have this issue.

I tried the suggested deletion of longtasks and longtaskparams tables, but it made no difference.

Is it possible to just delete the sqlite db, re-scan and let WP Toolkit rebuild it? Or just remove / reinstall the extension?

If not, I guess I'll have to contact support.

Some of my licenses are purchased from a reseller (Vultr US), but I'm not sure that they would have specific Plesk knowledge to solve this issue.

Any other suggestions to try first?

Thanks in advance for your advice.
 
Hi just to chirp in a little as well. Same scenario.

extension/wp-toolkit [3656942:65559b7d8f57e]
Failed to find corresponding domain for WordPress installation #27 ('http://www.deletedclientdomain.com'): Failed to find domains by instance.

extension/wp-toolkit [3656942:65559b7d8f57e]
An error occurred while executing WP-CLI command for instance: WordPress installation #27 ('http://www.deletedclientdomain.com'). Unable to find row with id 44 in domains table.

Appears the clean-up-after-yourself routine isn't quite a thorough as it could/should be.

Might help pinpoint it further: in above case, the customer itself was deleted. In Plesk itself, not via any API. [Obviously including his subscription, and the WP install in it].
 
Back
Top