Vagrant returns Nginx configuration page

[aeblin]

Having some issue running this locally after following the read-me's instructions for getting it up and moving with Vagrant. After running 'vagrant up', heroku.local/ fails to resolve.

The Vagrant box is running, and hitting the IP specified on line 4 of the Vagrantfile (192.168.50.100) returns a page saying that nginx is running and needs further configuration.

All that said, this is my first real foray into Vagrant, so it's entirely possible I'm missing something.

[xyu]

So the latest Vagrant should have modified your hosts file so that heroku.local resolves to 192.168.50.100. I'm not sure why it's not doing that. What OS are you using?

If it's OS X / Unix try adding the following to your /etc/hosts file.

192.168.50.100  herokuwp.local

[aeblin]

I'm on OSX, and modifying /etc/hosts did seem to work. Not sure why it'd be behaving that way. Either way, my immediate issue is resolved. Curious if anyone else has run into something similar?

[aeblin]

Actually, quick update here. After doing a quick vagrant halt, vagrant up - herokuwp.local/ still resolves, but now returns nginx's "further configuration is required" welcome page, instead of Wordpress. Seems like something may not be quite right with the Vagrant set up.

[xyu]

Can you do vagrant destroy then vagrant up and gist the logs or any errors in your error logs?

[aeblin]

Oh man, weird, weird, weird. So I did vagrant destroy and vagrant up once and got the nginx "further configuration is required" message. Just did it again to get logs for you - on the same branch - no "further configuration is required" message this time, just WP's default setup page.

Here's the logs from the successful attempt.
https://gist.github.com/aeblin/6287133a08cb82b1c520

And the logs from the attempt just prior that resulted in the "further configuration is required" message.
https://gist.github.com/aeblin/8aace6c09e9a66ab704a

Worth noting these both happened from the same branch, with no code changes, and using the same terminal window.

[xyu]

Yeah that's weird, I'm not seeing any failures in the unsuccessful run. Just out of curiosity what's your Vagrant version and are you using VirtualBox or some other provider?

Edit: Ignore the second part from your gist it looks like you are using VirtualBox, what version of that are you running?

[aeblin]

Running VirtualBox 4.3.20 and Vagrant 1.7.2.

Things are still very inconsistent as to whether or not herokuwp.local/ resolves between vagrant halt and vagrant up - really strange issue.

Edit: Here's a gist of a failure I received on vagrant up after vagrant halt
https://gist.github.com/aeblin/76e47ea91324f9f1d6e4

[xyu]

@aeblin Interesting, so I wasn't able to reproduce this issue however from your logs it looks like your VM was not able to mount the shared folder to /app within the VM. Maybe try reinstalling Vagrant and VirtualBox?

Relevant log lines:

==> herokuwp: Exporting NFS shared folders...
==> herokuwp: Preparing to edit /etc/exports. Administrator privileges will be required...
==> herokuwp: Mounting NFS shared folders...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mount -o 'vers=3,udp' 192.168.56.1:'/Users/aeblin/heroku-wp' /app

Stdout from the command:



Stderr from the command:

stdin: is not a tty
mount.nfs: access denied by server while mounting 192.168.56.1:/Users/aeblin/heroku-wp

[dmtintner]

It also did not add heroku.local to my hosts file. After manually adding that line, it worked fine

[xyu]

This thread is pretty old and I just rebuilt the Vagrant environment in af3cd22 to fix a bunch of outstanding issues. The README was also updated in 17826d0 along with new configs for the vagrant-hostmanager plugin is that's installed to automatically manage the hosts file on the host computer.

Given all those changes I think the issue encountered here should be resolved so I'm closing this issue.