Vagrant ssh connect to host 127.0.0.1:2222 port 22: Bad file number

ssh vagrant vagrant-windows
eComEvo picture eComEvo · Feb 27, 2015 · Viewed 8.5k times · Source

Whenever I try to connect to my local Vagrant, I get this error when I run ssh [email protected]:2222 from the Windows git bash:

ssh: connect to host 127.0.0.1:2222 port 22: Bad file number

It was working previously, so I'm not sure what could have caused this. When I try to do an SFTP connection in PHPStorm 8, I get this error:

Connection to '127.0.0.1' failed.
SSH_MSG_DISCONNECT: 2 Too many authentication failures for vagrant

I've tried vagrant destroy with vagrant box remove laravel/homestead and then recreating the box from a backup I had that previously worked using vagrant box add laravel/homestead homestead.box but I still get the same errors.

I'm on Windows 7.

What can I do to get access to my vagrant box commandline again?

Answer

aflorezd picture aflorezd · Feb 27, 2015

Try command:

ssh -p 2222 [email protected]

Related questions

How to fix Vagrant error: `private_key_path` file must exist:

I've been using PuPHPet to create virtual development environments. Yesterday I generated a config file for a new box. When I try to spin it up using the vagrant up command, I get the following error message: C:\xx>…

Read More
Vagrant stuck connection timeout retrying

My vagrant was working perfectly fine last night. I've just turned the PC on, hit vagrant up, and this is what I get: ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration... default: …

Read More
Vagrant ssh authentication failure

The problem with ssh authentication: ==> default: Clearing any previously set forwarded ports... ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration... default: Adapter 1: nat default: Adapter 2: bridged ==> default: Forwarding ports... default: 22 =&…

Read More