• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Domain failed to create

V

vinoveritas

Guest
Hello -

I had a domain fail on creation. The DNS module failed with an unknown error. Now, after a reboot, when I try and create that same domain again, it says that there are already DNS records for this domain. When I check the Microsoft DNS, there is nothing listed under forward or reverse.

I think the database is out of sync with what is actually there. How do you pull the bad data out of the database? I think it's using the MSSQL Server Runtime (whichever it chooses from a default install).

Thanks for the help!
 
Found Solution

FOUND SOLUTION:

I found that the tables for Plesks internal database are in a MySQL\Data folder located in the plesk install directory.

I used the command line tool, dbclient.exe, to find the out-of-sync records in tables: dns_zone & dns_recs. I issued the DELETE SQL command to remove them from the two tables.
 
Back
Top