I will tell you a little secret, you taught me more than that one command for CLI lol
One more important note for my Bitwarden
Thanks again bud!

I will tell you a little secret, you taught me more than that one command for CLI lol
One more important note for my Bitwarden
Thanks again bud!

OMG I guess that's what happens when you try to to work on two labs same time, I mixed the lab1 subnet I'm working on with the lab2 on my last mount attempt.
I changed it to the correct subnet and it mounted properly this time

Can it be that unmounting it in cli fixed the issue?
I am going to try the same unmount command on lab1 setup, and see if that will get it going also.

Thank you so much @Pilow . I appreciate the time and energy you spend helping me with this one!

xo@xo-ce:~$ mount -t nfs
xo@xo-ce:~$ sudo mount -v -t nfs -o vers=3 192.168.221.20:/LAB-NFS /run/xo-server/mounts/LAB-NFS/
mount.nfs: timeout set for Thu Nov 20 16:50:18 2025
mount.nfs: trying text-based options 'vers=3,addr=192.168.221.20'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.221.20 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.221.20 prog 100005 vers 3 prot UDP port 54698
xo@xo-ce:~$ mount -t nfs
192.168.221.20:/LAB-NFS on /run/xo-server/mounts/LAB-NFS type nfs (rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.221.20,mountvers=3,mountport=54698,mountproto=udp,local_lock=none,addr=192.168.221.20)
xo@xo-ce:~$ sudo umount /run/xo-server/mounts/LAB-NFS
xo@xo-ce:~$ mount -t nfs

So mounting in CLI seems to show it created a mount but i do not see it in the gui. so I unmounted it again and tried to remount in the gui remotes, its did add the remote but after a while, it gave a timeout error

{
"shortMessage": "Command failed with exit code 32: mount -o hard -t nfs 192.168.45.20:/LAB-NFS /run/xo-server/mounts/eecbb7da-e271-4c39-9681-5b50f8d65e9a",
"command": "mount -o hard -t nfs 192.168.45.20:/LAB-NFS /run/xo-server/mounts/eecbb7da-e271-4c39-9681-5b50f8d65e9a",
"escapedCommand": "mount -o hard -t nfs "192.168.45.20:/LAB-NFS" "/run/xo-server/mounts/eecbb7da-e271-4c39-9681-5b50f8d65e9a"",
"exitCode": 32,
"stdout": "",
"stderr": "mount.nfs: Connection timed out",
"failed": true,
"timedOut": false,
"isCanceled": false,
"killed": false
}

xo@xo-ce:/run/xo-server/mounts/LAB-NFS$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether c6:e3:43:a1:5b:e7 brd ff:ff:ff:ff:ff:ff
inet 192.168.221.24/24 brd 192.168.221.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::c4e3:43ff:fea1:5be7/64 scope link
valid_lft forever preferred_lft forever

What gets me is that if it was permissions related, theoretically, it should not mount the nfs storage SR with the same settings pointing to the xcpng host from the same qnap?!
It feels like something is different between the xoa nfs implementation and the xcpng host itself.
Dont you agree?

.22 XCP-ng host
.24 XOA
.115 Unraid server1 - Able to mount with no issues
.114 Unraid server2 - Able to mount with no issues

@Pilow That seems did the trick!
xo@xo-ce:/run/xo-server/mounts/LAB-NFS$ sudo mount -v -t nfs -o vers=3 192.168.221.20:/LAB-NFS /run/xo-server/mounts/LAB-NFS/
mount.nfs: timeout set for Thu Nov 20 15:42:55 2025
mount.nfs: trying text-based options 'vers=3,addr=192.168.221.20'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.221.20 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.221.20 prog 100005 vers 3 prot UDP port 54698
mount.nfs: mount(2): Device or resource busy
xo@xo-ce:/run/xo-server/mounts/LAB-NFS$ ping 192.168.221.20
PING 192.168.221.20 (192.168.221.20) 56(84) bytes of data.
64 bytes from 192.168.221.20: icmp_seq=1 ttl=64 time=0.884 ms
64 bytes from 192.168.221.20: icmp_seq=2 ttl=64 time=0.531 ms
64 bytes from 192.168.221.20: icmp_seq=3 ttl=64 time=0.507 ms
64 bytes from 192.168.221.20: icmp_seq=4 ttl=64 time=0.648 ms
64 bytes from 192.168.221.20: icmp_seq=5 ttl=64 time=0.496 ms
^C
--- 192.168.221.20 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4082ms
rtt min/avg/max/mdev = 0.496/0.613/0.884/0.145 ms
xo@xo-ce:/run/xo-server/mounts/LAB-NFS$

Why would it time out if it does mount nfs sr from the same qnap and same permission settings?! My head is starting to smoke lol

@Pilow seems the same error
xo@xo-ce:/run/xo-server/mounts/LAB-NFS$ sudo mount -t -v nfs -o vers=3 192.168.221.20:/LAB-NFS /run/xo-server/mounts/LAB-NFS/
mount: bad usage
Try 'mount --help' for more information.

@Pilow Sorry for the delay, bud, I was on the road all day yesterday.
I have to admit, when it comes to CLI I struggle.
I tried to figure out the mounting command as follows:
xo@xo-ce:/run/xo-server/mounts/LAB-NFS$ sudo mount -t nfs -o vers=3 192.168.221.20:/LAB-NFS /run/xo-server/mounts/LAB-NFS/
xo@xo-ce:/run/xo-server/mounts/LAB-NFS$ sudo mount -t -vvv nfs -o vers=3 192.168.221.20:/LAB-NFS /run/xo-server/mounts/LAB-NFS/
mount: bad usage
Try 'mount --help' for more information.

The mount command alone seemed to kick no error, but I do not see any remote/storage created in the gui.
When I try to add -vvv, it complains

-= Update =-
Tried to expose the Unraid server container to the host network, everything seemed perfect and pings work both ways, while nfs still giving me the same error only for mounting remotes (both from QNAP and the same host Unraid server.

I decided to install another fresh XCP-ng host server just to eliminate my first host configuration, but I got the same result, remotes would not mount.

The last idea was to remove the XOA container VM running on the Unraid server and download the prebuilt XOA VM image directly from the XCP-ng host. This gave me a timeout error when trying to mount off QNAP with permissions set to both the new XOA IP and the XCP-ng host IP.
remote.test
{
"id": "7903a500-ee84-43dc-bd3e-b6c7abe8381b"
}
{
"shortMessage": "Command failed with exit code 32: mount -o hard -t nfs 192.168.45.20:/LAB-NFS /run/xo-server/mounts/7903a500-ee84-43dc-bd3e-b6c7abe8381b",
"command": "mount -o hard -t nfs 192.168.45.20:/LAB-NFS /run/xo-server/mounts/7903a500-ee84-43dc-bd3e-b6c7abe8381b",
"escapedCommand": "mount -o hard -t nfs "192.168.45.20:/LAB-NFS" "/run/xo-server/mounts/7903a500-ee84-43dc-bd3e-b6c7abe8381b"",
"exitCode": 32,
"stdout": "",
"stderr": "mount.nfs: Connection timed out",
"failed": true,
"timedOut": false,
"isCanceled": false,
"killed": false,
"message": "Command failed with exit code 32: mount -o hard -t nfs 192.168.45.20:/LAB-NFS /run/xo-server/mounts/7903a500-ee84-43dc-bd3e-b6c7abe8381b
mount.nfs: Connection timed out",
"name": "Error",
"stack": "Error: Command failed with exit code 32: mount -o hard -t nfs 192.168.45.20:/LAB-NFS /run/xo-server/mounts/7903a500-ee84-43dc-bd3e-b6c7abe8381b
mount.nfs: Connection timed out
at makeError (/opt/xo/xo-builds/xen-orchestra-202511150402/node_modules/execa/lib/error.js:60:11)
at handlePromise (/opt/xo/xo-builds/xen-orchestra-202511150402/node_modules/execa/index.js:118:26)
at NfsHandler._sync (/opt/xo/xo-builds/xen-orchestra-202511150402/@xen-orchestra/fs/src/_mount.js:68:7)"
}

BUT
If I configured a completely unsecured public NFS share on the Unraid server, I then managed to get it mounted successfully. (using the XOA vm running on the XCP-ng host.

When I changed the share to Private with granting permissions to the IP of the host and the XOA VM IPs, I get permissions denied yet again.

At this point, I'm at a loss, there must be a way to grant access to an IP and make it work with remote. Clearly, I know how to grant permissions as the NFS SR and the Unraid mount of the secured NFS from QNAP are working with no issues.

Must be something stupid I'm missing.