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

Question How to Filter Database Servers Available to Plesk Subscriptions

OWEUX LLC

Basic Pleskian
Hello!

Thank you in advance for your ideas on this issue.

Some of our Clients have their own separate database servers (AWS) which are meant to be "PRIVATE" and for their own use only. We can connect successfully and it all works just 'fine'.

The issue that we have is that when a user creates a NEW database or WP (or any app) all available servers can be selected. We would like to limit these "PRIVATE" database servers to their owner (subscriber) rather than letting anyone choose any one server at creation time and hope they choose the right one.

I hope this image illustrates the issue:

upload_2019-4-30_12-52-25.png
 
Back
Top