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

Duplicated MySQL

D

danielbogo

Guest
:rolleyes: I am facing serious problems when I will create
new database MySQL in Plesk 8.0.
System not accepts database Name
same for bill of different resale.

An example:
Resell (THE) it creates database with name (brasil)
Resell (B) it doesn't get to create database with name (brasil)

Alert system that database already exists!

That also happens for database users' name.

How that to solve?
 
You can't create databases or users with the same names under different client accounts, because the same database server is shared between all clients.

One way to solve the problem would be to prefix each database name or username with the name of the client, so there is no confusion, but unfortunately Plesk will not automatically handle this so clients or domain users can still use whatever names they like.

Alternatively, if it is important for a particular client to have their own database server, you could install a separate instance of MySQL on a different port and set it up as a "remote" database server. Clearly, this isn't feasible to do for every client.
 
My God!

Where will we stop?
ATTENTION SWSOFT!!!!! SOLVE THAT URGENT! THAT IS EXTREMELY NECESSARY FOR WHO CHOSE IN USING PLESK FOR RESALE.

ATTENTION SWSOFT!!!!! ALERT YOUR FUTUROS CLIENTES ON THESE YOU FAIL!
 
Which the providence that SWSoft will take?
Will it be that SWSoft will repair that?
Will it be that SWSoft worries about that?
 
Has anybody told this issue to SWsoft support? I am wondering what they say about this because I saw some people saying the same thing on some other threads in the Forum.
 
Back
Top