nextcloud vagrant

[torches]

I setup a nextcloud via vagrant and I am able to reach ports 22,80,443 via the bridged ip from outside the guest but not 389 (ldap) as well as other ports. selinux is disabled, as well as the firewall. Anyone knows the reason for this behavior?

 

[vagrant@nc ~]$ netstat -na | grep -w 389
tcp        0      0 0.0.0.0:389             0.0.0.0:*               LISTEN    
tcp6       0      0 :::389                  :::*                    LISTEN    

my Vagrantfile:

    nc.vm.box = "ale_polidori/Nextcloud"
    nc.vm.network "public_network", ip: "192.168.86.68"
    nc.vm.hostname = "nc"

[Alvaro Miranda Aguilera]

in the old days, some services had bind options and also allow/deny parameters

you could check for each of those services if you can telnet the port

and check documentation for each of those, could be /etc/hosts.allow /etc/hosts.deny or the same service having an allow/deny setting

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/002bdf57-2c78-4c68-a4f7-d7da198e0792%40googlegroups.com.

--

Alvaro