Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trialSusan Parker
14,473 PointsInstalling Laravel: Missing host path on desktop & connection reset by peer on laptop.
On my desktop... The keys were created as github_rsa for some reason, instead of id_rsa so I fixed that. It had also stopped recognizing any vagrant commands in my terminal . This happened after running CC cleaner and it detecting over 1,000 registry issues with vagrant gems. So I re-installed Vagrant. I then ran "vagrant up" again. It attempted to load it but stopped saying that the "host path of the shared folder is missing : ~/Code" .
On my laptop, after renaming the keys from "github_rsa" to "id_rsa" like I did on my desktop, I got it to run the "vagrant up" but it kept timing out on the connection. When it was done running the time out errors I tried again and it said that my VM was already running. So I did the "vagrant ssh" command and it gave me this "ssh_exchange_identification: read: Connection reset by peer".
Susan Parker
14,473 PointsThis is what my .yaml file looks like, if that helps any.
ip: "10.0.10.10"
memory: 2048
cpus: 1
provider: virtualbox
authorize: /Users/strawberryburns/.ssh/id_rsa.pub
keys:
- /Users/strawberryburns/.ssh/id_rsa
folders:
- map: /Users/strawberryburns/Homestead/Projects
to: /home/vagrant/Sites
sites:
- map: laravel.dev
to: /home/vagrant/Sites/laravel-basics/public
databases:
- homestead
variables:
- key: APP_ENV
value: local
2 Answers
Christopher Rebacz
10,904 PointsA couple of things:
First the folder error you are getting is often due to the fact that the Code folder has not yet been created inside the Homestead folder when running vagrant up. Create that folder and then run Vagrant up to see if that resolves the issue.
Second, im thinking you probably will need to regenerate the rsa tokens. Those are needed for authorization when running using ssh. The installing Laravel lesson from laravel basics here is really good at explaining how to create those tokens. Renaming might work but if you are using github, you will start getting errors whenever you try to push code up to github.
Christopher Rebacz
10,904 PointsSorry... just saw your Yaml file and noticed you have your local path set to Homestead/projects, which means that my recommendation to add a code folder won't work. I don't see any reference to a Code directory in your Yaml file I'm not sure why you would get that error with this file. Since that is the default path when using homestead, im wondering if you have a second Yaml file. Recent versions of homestead create a directory at ~/.homestead and place the Yaml file there. Earlier versions of homestead included the Yaml file at the root of the Homestead folder where you would add your projects. Since you had reinstalled Homestead as part of your cleanup but hadn't deleted the Homestead directory with your projects, it is conceivable to have both Yaml files present. If it is the case that you do have a second Yaml file, just copy your configurations from this one into the one inside the .homestead directory.
Susan Parker
14,473 PointsSusan Parker
14,473 PointsI'm running Windows 8 on the desktop, and the laptop is older and running Vista.