Sorry for the poor formatting. Hopefully this will be more readable:

Chriss-MacBook-Pro:Homestead username$ vagrant destroy
    default: Are you sure you want to destroy the 'default' VM? [y/N] y
==> default: Destroying VM and associated drives...

Chriss-MacBook-Pro:Homestead username $ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'laravel/homestead'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'laravel/homestead' is up to date...
==> default: There was a problem while downloading the metadata for your box
==> default: to check for updates. This is not an error, since it is 
usually due
==> default: to temporary network problems. This is just a warning. The 
problem
==> default: encountered was:
==> default: 
==> default: The requested URL returned error: 404 Not Found
==> default: 
==> default: If you want to check for box updates, verify your network 
connection
==> default: is valid and try again.
...
==> default: Running provisioner: shell...
    default: Running: inline script
    default: Failed to restart php5-fpm.service: Unit php5-fpm.service not 
found.
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.



I believe this is causing my boxes to respond to ping, but not curl:
Chriss-MacBook-Pro:Homestead username$ ping testing.app
PING testing.app (192.168.10.10): 56 data bytes
64 bytes from 192.168.10.10: icmp_seq=0 ttl=64 time=0.458 ms
64 bytes from 192.168.10.10: icmp_seq=1 ttl=64 time=0.305 ms
64 bytes from 192.168.10.10: icmp_seq=2 ttl=64 time=0.307 ms
^C
--- testing.app ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.305/0.357/0.458/0.072 ms
Chriss-MacBook-Pro:Homestead username$ curl testing.app
<html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx/1.11.9</center>
</body>
</html>

and of course, if it won't respond to curl, it won't respond to a browser!

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/9b147359-09a1-4610-929f-4fdfc691e437%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to