Hi Robert, So if you look at your Vagrantfile, you have the db00 host performing port_forwarding from the host 15432 to the guest 5432. However, judging by your netstat output (from within your db00 VM) it looks like Postgres is listening on 15432.
So there is no way web00 nor the host will be able to reach db00 (postgres). Port forwarding is for the benefit of the host (you don't need it if you only care about web00 to db00 connectivity (the private network will suffice). So if postgres is listening on 15432 (and will accept connections from 0.0.0.0), then from web00 you can do 'telnet 192.168.2.101 15432' and it should allow a connection. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/b72f3b0d-b439-4ebd-ae30-2047bf47a4a0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
