• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

unable to remove domain Plesk misconfigured

R

rdenis

Guest
Hi there I am trying to remove a domain from Plesk 8.3.0

I get this error message



Service Unavailable

Service is not available now, probably your Plesk is misconfigured.
Contact Your provider for details.

Internal Plesk error occurred: Dashboard preset used by user failed: DashboardPreset: unable to select: no such row in the table

I checked the vhost folder and the domain is not even there..

I tried creating a dummy domain and renamed it to the one that I can't delete same error

I checked the knowledges base and nothing....

I did a complete search in this forum but didn't find anything with the exact error message.. I found some unable to remove domain and the search options really sucks

you cannot put more than 3 words in the search box.. so you need to spend hours finding

a solution and looking for previous topic trying to look for your exact error messages

we have 6 plesk servers with our company and the support is terrible


I had this error message many times before and it's comon and all I ever did was freggin reclone the VPS with another one just to save time.. because I was fed up.

Sly..
 
That error means that there is no database row associated, try looking into the psa DB and find the IDs that are being looked at, and change the IDs of your dummy domain to correlate, that should allow the DB referential integrity to resume.
 
Back
Top