-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Root mysql login not working #453
Comments
Please fill out the entire issue template so we don't have to ask you what versions of everything you're using to properly help you. https://github.com/laravel/homestead/issues/new |
Hi @svpernova09, here are the details, just so you know, it may be 'settler' related, same problem with box version 1.1.0 and 1.0.1 I have tested with 0.2.7 and it works just fine, haven't tested any other box versions. Versions
Host operating systemWindows 10 Homestead.yaml---
ip: "192.168.10.10"
memory: 2048
cpus: 1
provider: virtualbox
authorize: ~/.ssh/id_rsa.pub
keys:
- ~/.ssh/id_rsa
folders:
- map: ~/projects
to: /home/vagrant/projects
sites:
- map: cybertill.app
to: /home/vagrant/projects/info |
Yep, the issue is in settler. Here https://github.com/laravel/settler/blob/master/scripts/provision.sh#L186-L189 we are setting This will require a box update to fix, but in the meantime you can add this line to your Homestead
|
Also worth mentioning the
|
Thanks @svpernova09 will try it out tomorrow, I understand the benefits of using the homestead user, however, I am tied to an app that requires root access. |
no worries, the one liner #453 (comment) in that comment should get you fixed up. |
Thanks @svpernova09, however, I am getting this error with the 'one liner' mysql: [Warning] Using a password on the command line interface can be insecure. |
You have to run it as the
|
thanks @svpernova09, works really well |
I updated to the latest version of the Homestead box and am no longer able to login to mySQL as root, I used to do it using 'secret' as the password, has something changed?
The text was updated successfully, but these errors were encountered: