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

Plesk unable to drop database that was dropped and then recreated via command line

H

help-please

Guest
Plesk is having trouble dropping a database that was dropped and then recreated using the postgres dropdb and createdb command.

The database was initially created within Plesk. We disconnected it from Plesk somehow when we ran the dropdb and createdb command from the command line. Plesk no longer recognizes the newly created database. If we try to drop the database from Plesk it throws errors. If we drop the database that we created via command line, Plesk still sees the database. I just want to start over and recreate the database in Plesk.

Does anyone know how I can fix this problem?
 
Back
Top