# \[SOLVED\] NFS mount hangs - need Vagrant file for Fedora 23

**URL:** <https://meta.discourse.org/t/solved-nfs-mount-hangs-need-vagrant-file-for-fedora-23/41314>\
**Category:** Self-hosting\
**Created:** [March 19, 2016, 6:01pm UTC](https://meta.discourse.org/t/solved-nfs-mount-hangs-need-vagrant-file-for-fedora-23/41314 "2016-03-19T18:01:34Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![JimmyX](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jimmyx/32/52302_2.png) [@JimmyX](https://meta.discourse.org/u/JimmyX)\
**Post date:** [March 20, 2016, 4:51am UTC](https://meta.discourse.org/t/solved-nfs-mount-hangs-need-vagrant-file-for-fedora-23/41314/2 "2016-03-20T04:51:30Z")

</div>

I found a post here which explains which services you need to allow through the firewall in order for vagrant to work.

[https://github.com/mitchellh/vagrant/issues/2447](https://github.com/mitchellh/vagrant/issues/2447)

> Example for easily configuring firewalld using the “firewall-config” GUI:

> ```
> choose "Configuration: Permanent" from the drop down menu
> select the zone you want to modify (i chose "internal").
> go to the "Interfaces" tab, assign vboxnet0 (or other host-only adapter) to the zone.
> go to the "Services" tab, check "mountd", "nfs" and "rpc-bind"
> go to the global "Services" tab (next to "Zones"), select NFS and add Port 2049 UDP (only TCP is predefined).
> Finally choose "Options/Reload Firewalld".
> 
> ```

> NFS mounts now work correctly from within the VM and you can leave firewalld enabled.

I had trouble with SELinux which I resolved by deleting the .old files in /etc/firewalld/zones

I managed to get “vagrant up” working and “vagrant ssh” to get in. I got discourse up and running.

---

_[View the full topic](https://meta.discourse.org/t/solved-nfs-mount-hangs-need-vagrant-file-for-fedora-23/41314)._