NFS share fails to connect when secondary interface is active

Installation
1

Hello,

I have an odd one here. I am working on setting up a new Home Assistant server on my new Proxmox server. I already run one on my old server but this will be a rebuild from the ground up to clean out the various messes I have made over the years.

One of the things I am setting up on the new server is use of a wildcard cert from LetsEncrypt. The cert gets managed by my OPNSense router and that is working fine. It then pushes it out to a folder on my NAS that I share out to all my VMs and LXCs with NFS. I have that setup working on about 5 or 6 different systems now and it works well.

I’ve setup my new Home Assistant VM based on the standard instructions for running HAOS on a VM and that is working well for the most part. So latest OS version and latest HA version. I have added the NFS share in the storages section and then set the SSL settings in the config file. Again worked fine. I can access the HA instance via SSL under the host and port I specified.

Now comes the strange part. I am trying to add a 2nd network interface to the VM. On my Proxmox setup I have an SDN defined for VM-to-VM communication so that type of traffic doesn’t have to go over my physical network. It is currently used for the VMs to access the MariaDB sever I have setup on the Proxmox server. Added the NIC to the VM is fine but as soon as I assign an IP to the interface the NFS share disconnects and I cannot reconnect it. Remove the IP and it works fine. They are not using the same subnet my physicla is 192.168.1.x and my SDN is 192.168.100.x all using /24. The SDN interface I do not assign a gateway as there is none.

I know there are several other ways to set this up but this is the way I am hoping to work this. I am really hoping to be able to point HA to the mariadb server over the SDN network and let everything talk to it via the main network.

This is the message that showed up in System > Logs (replaced storage name for security reasons):
Failed to to call /mounts//reload - Reloading did not succeed. Check host logs for errors from mount or systemd unit mnt-data-supervisor-mounts-.mount for details.
Any help is appreciated.

I tried to find the logs mentioned but not sure how.

2

Couple of things to try:

  • if your NFS Share is referenced in HA by name, SSH into your HA server and ping your NFS server by name.local, and if it fails, ping it by IP address.
  • SSH into your HA server and see what the routes are by using: ip route
3

First, thank you for replying.

Second, I hate computers. I am an IT guy for a living so I am allowed to say that. lol

The reason I hate them this time, I went to go try your suggestions. I installed the SSH add-on, connected, was able to ping by hostname and IP, and all my routes looked good. This was with the inteface not configured (pre-check). Then I configured it as noted above and… it worked. No issues. Rebooted, no issues. I swear I did this like 6 times before and kept having the issue. This time for some reason it is working. Not very confident in the setup but I will go with it for now.