Hello, My name is Alvaro Miranda, and I will like to help you on this.
However, I believe is going to be easier for both start from scratch and forget about fix/troubleshoot that actual system you have. with this idea in mind, if you can share with me the following: - Vagrantfile you are using. create a gist on put it on github and share link please - brief description of what you expect to have after this VM came up - brief description on what is not working and you think it should I believe if go in this way, we will make progress fairly quick thanks, Alvaro. On Thu, Jul 10, 2014 at 6:30 AM, Malik Rumi <[email protected]> wrote: > I am having the same problem described here > <https://groups.google.com/forum/#%21topic/vagrant-up/aR9crryDmzU>, but I > have a slightly different setup and less experience. I have wsgi and > gunicorn but not nginx - besides, none of the similar problems I've seen > posted here have acknowledged, definitive resolutions posted. > > I got this vagrant precise64 box from 'getting started with django' > because I am on a Windows 8.1 machine. At first, it worked fine, then, none > of my projects came up in a browser on the host. Chrome says I got an > 'empty response', Firefox says the connection was reset, and IE says the > page cannot be displayed. The folks at GSWD don't respond very frequently > on their forum so I've given up on that. I posted on the Ubuntu forum and > SO before that, no luck so far. I found this post > <http://stackoverflow.com/questions/5984217/vagrants-port-forwarding-not-working> > in reply to someone else on SO. The selected answer said to run a curl > test, I did and the connection was refused. This answer says if the curl > test fails, it is not a port forwarding problem, but that doesn't tell me > what the problem is or how to fix it. > > There is another answer to the SO post I just linked to, which has been > upvoted more than the selected one. That one says that the problem is > caused when the server inside the VM binds to 127.0.0.1, and points out > that some dev servers like Django's default to that same address. His > solution is to bind the server to 0.0.0.0. (The editors at SO closed the > whole thing down as 'off topic', which I think they do waaaay too often, > but I digress). > > The vagrantfile config.vm.forward port is (8000, 8888), not (80, 8080), if > that is significant. Under port forwarding rules in the VM, the rule named > 'ssh' has a host ip of 127.0.0.1, host port 2222, guest port 22. I just > don't know if this is the 'binding' that the SO answer was talking about or > something different? I understand that this is how I am making the ssh > connection, but is this "binding"? If I change that to 0.0.0.0. does that > solve my problem or break my ssh connection to the VM? > > Thx. It would be nice to see my site locally instead of only on Heroku. > > -- > 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 [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
