Thanks Rob - with a wget I get this on the first console [23/May/2014 18:19:16] "GET /Arches/index.htm HTTP/1.1" 200 18088
and this on the second 2014-05-23 23:19:16 (25.3 MB/s) - `index.htm' saved [18088] so it seems to be working! I'll have a look at the networking / forwarding. Andy On Friday, 23 May 2014 21:47:37 UTC+1, Rob Gaston wrote: > > Hi Andy, > > 'vagrant destroy' then 'vagrant up' should get you a fresh VM; no need to > delete your local repo. > > Sounds like it might be a port forwarding issue (as the server looks to be > running just fine). Is it possible that port 8000 is already in use on > your host system? > > Vagrant sets up port forwarding as one of the first steps following > 'vagrant up' -- the output should tell you if it was successfully able to > forward ports as described in the VagrantFile ( > https://gist.github.com/robgaston/10031103#file-arches_vagrant_setup-log-L44-L49). > > If port 8000 is occupied, you can modify the VagrantFile to use another > port on your host system ( > http://docs.vagrantup.com/v2/getting-started/networking.html). > > You can verify that the server is returning pages by creating a new ssh > session into your VM (leave the one running the server up, or else it will > bring the server down) and using curl or wget to request a page from > http://0.0.0.0:8000/Arches/index.htm > > - Rob > > -- -- To post, send email to [email protected]. To unsubscribe, send email to [email protected]. For more information, visit https://groups.google.com/d/forum/archesproject?hl=en --- You received this message because you are subscribed to the Google Groups "Arches Project" 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.
