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 trial

PHP Laravel 4 Basics Laravel and Databases Database Setup

Curtis Black
Curtis Black
2,829 Points
Posted by Curtis Black
Curtis Black
2,829 Points

vagrant ssh no longer works. How do I fix this?

Curtis@BLACK-FAMILY-PC ~/homestead/projects (master) $ vagrant ssh VM must be running to open SSH connection. Run vagrant up to start the virtual machine.

Curtis@BLACK-FAMILY-PC ~/homestead/projects (master) $ vagrant up Bringing machine 'default' up with 'virtualbox' provider... ==> default: Checking if box 'laravel/homestead' is up to date... ==> default: Clearing any previously set forwarded ports... There was an error while executing VBoxManage, a CLI used by Vagrant for controlling VirtualBox. The command and stderr is shown below.

Command: ["modifyvm", "a7826950-1e32-4f18-8066-d5e3575df152", "--natpf1", "delet e", "ssh", "--natpf1", "delete", "tcp33060", "--natpf1", "delete", "tcp54320", " --natpf1", "delete", "tcp8000"]

Stderr: VBoxManage.exe: error: Failed to assign the machine to the session (E_FA IL) VBoxManage.exe: error: Details: code VBOX_E_VM_ERROR (0x80bb0003), component Mac hine, interface IMachine, callee IUnknown VBoxManage.exe: error: Context: "LockMachine(a->session, LockType_Write)" at lin e 471 of file VBoxManageModifyVM.cpp

Curtis Black
Curtis Black
2,829 Points
Curtis Black
Curtis Black
2,829 Points

I figured it out... It was because I had run the git bash in a later session as administrator, but set it up with a regular open, which probably changed the home directory. So, I opened git bash normally and went to my homestead folder and got it to work.