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

Problem with Plesk and MySQL DB's

L

Leighm0

Guest
I have just recently found a bug with plesk 8.1 for windows which involves the creation of mysql db's.

I have never had domains with numbers at the beginning but now a client has joined with one and normally when we add them into Plesk we create the domain/client, the username is normally the domain name without the .com etc.. and then we normally create a db with the same name and all ftp username and db username etc etc.. so its all pretty much uniform so its easy for us and easy for client to remember etc.

The mySQL db errors like so when using a numeral at the start of the db name: Error connecting to mySQL server... at which point i was curious because it was running fine.. so I went to the Event Log on server under Plesk and found the following:

Failed to connect to database: Can't connect to MySQL server on 'localhost' (10061)
at (MySQLDatabaseProvider::connect line 213)
at execute console command --check(vconsoleapp: tart line 128)
at execute "C:\Program Files\SWsoft\Plesk\admin\bin\mysqlmng.exe" --check "--server=localhost" "--port=4companyname" "--login=admin"

It was using the database name i had chosen for the Port.. kind of odd since shouldnt it be 3306.. and why in the heck was plesk telling the command line that the port was the db name.. interesting..

Anyway so i made it without the number 4 infront, and then also found out it wouldnt let me create a username on mysql access with a number either..

I guess its no real big issue, all i did was change all the other usernames to not inlcude the 4 so its all uniform like we have for all clients... but it was kind of silly that it screwed up the way it did..
 
Back
Top