Anybody?

Your login should be taken care whenever you added your id_rsa and id_rsa.pub in your Homestead.yaml file.

Can you post your Homestead.yaml, your Vagrantfile and what OS you're using?

Ubuntu 14.04 -- updated

Homestead.yaml:

---
ip: "10.0.10.10"
memory: 2048
cpus: 1

authorize: /home/mhm5000/.ssh/id_rsa.pub

keys:
    - /home/mhm5000/.ssh/id_rsa

folders:
    - map: /home/mhm5000/Homestead/Projects
      to: /home/vagrant/Projects

sites:
    - map: laravel.dev
      to: /home/vagrant/Projects/laravel-basics/public

variables:
    - key: APP_ENV
      value: local

Vagrantfile:

VAGRANTFILE_API_VERSION = "2"

path = "#{File.dirname(__FILE__)}"

require 'yaml'
require path + '/scripts/homestead.rb'

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
  Homestead.configure(config, YAML::load(File.read(path + '/Homestead.yaml')))
end

& After Forwardeing Ports:

==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.

changed the ip to 198.168.10.10 still the same problem...

if you are using a 32bit ubuntu : open the file: Homestead/scripts/homestead.rb and after vb.customize ["modifyvm", :id, "--natdnshostresolver1", "on"] add this line:

vb.customize ["modifyvm", :id, "--ostype", "Ubuntu_64"]

didn't work! Anybody else?

Hello MHM5000, same problem here. Have you had any luck?

If I turn off the wifi before 'vagrant up', it'll apparently start correctly. But this is not the proper way to solve it, though.

No, I changed to Python and Django... much easier much faster...