how to change caching\_sha2\_password to mysql\_native\_password on a digitalocean's managed mysql database?
i want to use the new digitalocean mysql managed databases with my php application but i’m getting this error here: er\_not\_supported\_auth\_mode: client does not support authentication protocol requested by server; consider upgrading mysql client could anyone please let me know how can i change the authentication type for my *mysql *user from caching\_sha2\_password to mysql\_native\_password? thank you!
hello, the easiest way to fix that would be to alter your existing user with the following: alter user myuser identified with mysql\_native\_password by 'mypassword'; another thing that you could do is to create a new user with mysql\_native\_password. to do that you could use the following: create user 'your\_user'@'your\_server\_ip ' identified with mysql\_native\_password by 'your\_password'; also as mentioned by @kavo13, try to upgrade php to 7.2 as well. after that, it should all work as normal. i’ve created a quick video demo on how to do that: i’m running the test on an ubuntu 18.04 droplet. hope that this helps! regards, bobby
we can’t, i am sorry. send an email from the same email address that was associated with your account to 
support(/@)[cloudflare.com](http://cloudflare.com) 
the trust and safety team will take care of it, but be prepared to answer a lot of questions. 
meanwhile you could change the nameservers for your domain back to those… a search for other 1106 error posts shows you really do need to contact support, as it says. 
[login to cloudflare](https://dash.cloudflare.com/login) and then [contact cloudflare support](https://dash.cloudflare.com/?account=support) by clicking on the get more help button. it's not in the core, but you can use an app: <https://apps.owncloud.com/content/show.php/registration?content=170608> Hello,

 

 

We would like to inform you that decoding MCE errors is out of the scope of support for us. As a general recommendation based on the wording for the log, please check the memory modules installed and confirm if one of them has failed.
 
 
 
 
 
 
 
 
 

[View solution in original post](/t5/Server-Products/How-to-decode-MCE-errors/m-p/527769#M13599) hello and welcome [@jhmauritz](/u/jhmauritz).

yes, changing the variables should be enough to connect to the server, and using docker-compose is absolutely a viable option.

if the server is publicly available you should configure ssl as well, otherwise your connections to it won’t be secure.

mind that although y… see this link for account handling:https://support.sonos.com/s/article/3427?language=en\_usyou will find help for changing accounts, resetting passwords, etc. i encountered the same problem as you with mamp's mysql server. i think the source of the problem comes from setting the mysql port to 3306. i went through the same stack overflow solutions that you indicate but none of them fixed the issue. i then decided to reinstall mamp and reset the ports to default before launching the server for the first time (after reinstalling) and it worked. unfortunately, this means that the option to run wordpress locally using the folder's name as a url won't work :( 
wish you the best of luck finding a solution to this problem! if you do, it would be greatly appreciated if you could share your findings :) [orafik](/members/orafik) thanks, unfortunately this is for an older version that i am not using. i actually found one 

<https://support.solarwinds.com/successcenter/s/article/setup-ssl-and-enable-smart-card-cac-pki-user-authentication-for-orion-web-console?language=en_us> Hi  

This is simple. First check whether you are able to connect Sql Server through SSMS or not.If you are able to connect through SSMS, then there may be a problem in connection string. If you are not able to connect through SSMS, then you had some problem with SQL Environment. if the server is that old then you'd likely be looking at sql server nearly the same vintage (perhaps sql 2008), you should be able to install a personal edition of 2008 sql on that, run a simple bak file restore with no problem.as stated though, those are well out of support (as you likely know) so it should be a priority that you get both slated for replacement.you mention audit, so i'd wager we are talking at least a public held company. definitely look towards a migration to newer software/hardware for security issues.