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

Issue GetDatabases Rest API Fatal Error

safemoon

Regular Pleskian
Server operating system version
Ubuntu 24.04.2 LTS
Plesk version and microupdate number
Plesk Obsidian 18.0.68 Update #2 Web Host Edition
Hi All,

Recently the API call to the /databases endpoint is not working properly without a "domain" parameter.
It used to work without any issues before.

Having the ability to find if a database name already exists in the server is very beneficial as it allows you to create databases/domains etc remotely without conflicts.
Is there any other way to check if a string of database name already exists in the system?

URL: <serverurl>:8443/api/v2/databases
Response:
JSON:
{
    "code": 0,
    "message": "PleskX\\Api\\Operator\\Database::getAll(): Argument #1 ($field) must be of type string, null given, called in /opt/psa/admin/plib/modules/rest-api/v2/library/SDK/pm_Database.php on line 47"
}

From my understanding it's a Fatal error on Plesk's API Files as the empty/non existent "domain" parameter is not handled properly.
@IgorG
 
Also the endpoint /dbusers does NOT work without a string query "dbId"
It used to work fine previously. It seems like a lot has changed in the API in the last few weeks, particularly in the databases from what I can see.

However, this is not good because now we have to make a lot more API calls and nested for loops just to check if a database user or a database exists before creating a new one.
 
Back
Top