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

8.1.1 Failed domain creation

W

wardjame

Guest
After running the upgrade to 8.1.1 I am receiving the following error when I attempt to create a new domain:
ERROR: PleskFatalException
Failed domain creation: Unable to update domain data: There are incorrect parameter values.
0: /usr/local/psa/admin/htdocs/domains/create_domain.php:150

Anyone else seeing this? Any thoughts on how to fix it?
 
Plesk support solved this problem with the following explanation:
The problem was that the default DNS record for the webmail was missing in the server configuration and the domain creation using the template was impossible, however the domain creation without template was successfull as the webmail option is included in the template. I have added the default DNS record for the webmail, you can see it in Server > DNS settings.
 
Another Cause

I ran into this same problem today, but my dns_recs_t table appeared to be correct.

I finally tracked it down to invalid data in the client profile. The client's email address contained a trailing space (e.g., "[email protected] "). Plesk sends email notification to the administrator and client upon domain creation, so this bad data blocked the process. The error message is completely unhelpful and I couldn't find any error logging on the system.

Since Plesk validates the email address when the client profile is created or edited, I assume this problem cropped up if/when we edited the clients table on the back-end using mysql CLI or phpMyAdmin.
 
Back
Top