port_forwarding allows a port in the VM to be exposed to the host. So in your case, if you do port_forwarding with your Postgres process you want to expose your database to your host.
What I wanted to do was focus on only the necessary configurations and worry about port_forwarding later (because obviously, accessing the database is more important from web00 than it is for the host). Given that the nmap command failed from web00 to scan open ports on db00, it suggests that the database is rejecting connection attempts. nmap output says 'Host is up' which means that web00 can ping db00. Can you 1. verify listening_addresses configurations on postgres.conf and pg_hba.conf? 2. restart postgres, 3. show us netstat -tlpn? FYI, I'm assuming that you perform an 'apt-get install postgres' in your ansible provisioning. That you make edits to the configuration files, and then you restart postgres server. Perhaps, what you can do is, destroy the VM, build a new one manually (no provisioning by ansible). And verify as you go that you can reach the VM from inside and from outside of it. -- 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/42afa05c-7c3f-41cb-a1d6-df238a12471a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
