Alright, maybe I'll need to up the scripts. For the iptables , all I can get is this: vagrant@vagrant:~$ sudo iptables --list-rules -P INPUT ACCEPT -P FORWARD ACCEPT -P OUTPUT ACCEPT vagrant@vagrant:~$
Re selinux. I tried getenforce and sestatus both return command not found There is a selinux conf file, only two lines un-commented module-store = direct expand-check=0 I don't believe I need VirtualHosts because I only have one site. Right now I have Niginx on guest 80, I can get the Nginx page at 8080 Web with Thin is running on 3000, can get at 4567. Putting aside possible problems in my conf file or vagrantfile, - from the tcp side if they are both running on 127.0.0.1 should Niginx be able to see the app server? Thanks FF On Tuesday, October 31, 2017 at 3:52:18 AM UTC-6, Alvaro Miranda Aguilera wrote: > > can you share a github repo of the Vagrantfile and the scripts? > > Can be se-linux can be iptables, can be listen, can be virtualhost, etc. > > so if you what you have, I can just vagrant up and test. > > alvaro. > > On Tue, Oct 31, 2017 at 1:32 AM, French Fry <samb...@gmail.com > <javascript:>> wrote: > >> I've tried a number of configurations , i.e. forwarding ports (guest and >> host) as well as a private network. Nginx listens on port 80. The Nginx >> server can be seen if I have guest: 80 and host: 8080. When I start up >> the web server it runs fine but Nginx seems to have no recognition of it. >> Without the private network they are both on 0.0.0.0 or 127.0.0.1 (as >> 0.0.0.0 resolves too anyway) as defined in the etc/host. With the private >> network, same deal. >> >> I'm trying to rule the possibility of something I might be doing wrong in >> Vagrant. Obviously I'm trying to do this via TCP , not sockets. If anyone >> knows ANYTHING to try I'd be happy to hear. >> >> Thanks >> FF >> >> -- >> 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+...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/vagrant-up/e4be3198-eb93-4067-9ab4-fe6529135c64%40googlegroups.com >> >> <https://groups.google.com/d/msgid/vagrant-up/e4be3198-eb93-4067-9ab4-fe6529135c64%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Alvaro > > -- 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/9448d48e-b71b-4aa7-a39d-2f85f382135b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
