Jump Start PHP Environment - Page 52

support
book

#1

Greetings,

On page 52 I issue the vagrant up command and get the following error:

A Google search further adds to the confusion on how to get past it.

Thanks,
KB


#2

...and I've been through this post to no avail: https://www.sitepoint.com/community/t/setting-up-vagrant-homestead-windows-8-1/266919/7


#3

What do you see in VirtualBox? Is the machine running? Can you open the machine there?

It looks like vagrant can't SSH into the machine, which can be caused by the machine not running or maybe a firewall that's in the way.


#4

Thanks for the reply.

I see the following:
1.

2.

3.

4.

5.

6.

  1. http://homestead.app produced this:

What would I look for firewall wise?

Thanks.


#5

...oh yeah, and this:


#6

What is image 5?

Also, in image 6 I see you're using the IP 192.168.10.10, but screenshot 4 says the IP of the machine is 10.0.2.15

Could you change the IP in your hosts file to 10.0.2.15 to see if that works?

As far as the firewall goes, there is either the windows firewall, or some proprietary software you've installed.


#8

5 is Homestead.yaml.

The IP change did not help, but thanks for the reply.

Take care,

kb


#9

Only a guess I'm afraid, but I wonder if this might have something to do with GitHub removing weak cryptography support?

https://developer.github.com/changes/2018-02-01-weak-crypto-removal-notice/

Did you install your version of Git before this February?


#10

Thanks for the reply.

Looks like I installed Git on 5/22/18.


#11

When I've seen people with this issue (and the machine has booted correctly) it's because of one of two things:

  1. UAC (or whatever it's called in windows these days). You need to make sure you press "Allow" on the various popups that appear when you run vagrant up.
    You might need to force VirtualBox to re-create the network adapter. Go to File > Host Network Manager. In the window select the network with the IP 192.168.10.1 and remove it. Run vagrant up again and make sure you press "Allow" on any popups.

  2. VPN. If you are connected to a VPN system wide, you won't be able to connect to local IP addresses like 192.168.10.10


#12

I removed the adapter, ran vagrant up and get the following NEW error:

There was an error loading a Vagrantfile. The file being loaded
and the error message are shown below. This is usually caused by
an invalid or undefined variable.

Path: C
Line number: 110
Message: undefined method `each'

Not sure what to make of it...line 110 in which file is my question.

And for #2, a majority of the time spent with this I have not been on VPN.

Appreciate your input Tom.

kb


#13

Nevermind, got the line 110 error sorted out.

Ran vagrant up again and see this:

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'laravel/homestead' is up to date...
==> default: Running provisioner: file...
Guest-specific operations were attempted on a machine that is not
ready for guest communication. This should not happen and a bug
should be reported.


#14

So I did a vagrant destroy then a vagrant up and I'm back to square 1 i.e.

default: Key inserted! Disconnecting and reconnecting using new SSH key...
default: Warning: Remote connection disconnect. Retrying...
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.

...and "This site can’t be reached homestead.app unexpectedly closed the connection."


#15

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.