• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved mysql_config_editor

kojot

Regular Pleskian
Hi,

I wrote some scripts, and it is very annoying because I'm getting message like this:
Code:
Warning: Using a password on the command line interface can be insecure.

and probably it's insecure.

I set --login-path= with mysql_config_editor but now I'm getting ERROR 1045 (28000): Access denied

I created that user from Plesk's phpmyadmin.

Last year I tried similar, and I had the same problem.
I know that Plesk already encrypt passwords, but I supposed that doing only for admin?

Can someone advise me how to setup --login-path?

Regards,
 
hm, someone resolved this thread before me?!

I already read that documentation, and I set it like it is described there.
But now I concluded that can't use special characters in password. I used # and !, and I logged in with that password without problem with mysql -u -p

Now I see in comments that someone also had problem with #.

Now thread can be "Resolved" ;)
 
Back
Top