Why does HA have a problem with this (Nextcloud AIO)?

1

TL;DR, CalDav / WebDav / Uptime Kuma fails (to connect / Authenticate) when HA and NC are on different NIC’s.

This effect is only with HA, as all my other Dav programs have no problem reaching Nextcloud.

System Topography…

Windows 11 Host with a 4 port NIC
VMWare Running 2 Clients. (HAOS and Ubuntu - Nextcloud AIO)

VMnet0 = Is one NIC used for HA
VMnet2 = Is one NIC used for NC AIO

The only way this works if both HA and NC AIO are on the same NIC or VMnet.

What has me confused is why does it even mater as the entered url that HA is requesting is reaching out an https (ssl) WAN site.

I’m confident I have something wrong in my configuration / setup, but for the life of me I can’t find it.

2026-01-26_11-35-03
2026-01-26_11-35-031084×929 46.2 KB

2026-01-26_11-35-27
2026-01-26_11-35-271343×1279 61.1 KB

2026-01-26_11-35-56
2026-01-26_11-35-561340×1278 72.1 KB

2

Are you having a general network subnetting issue, not a HomeAssistant specific one?

3

I’m not sure what I’m having… :slight_smile: The only problem I’m seeing is what I have described. ‘Everything’ else works well.

4

I have to believe others on windows have segregated VM’s, with Home Assistant and Nextcloud using dav or Uptime Kuma??

5

List the IP Address of each device (physical and virtual), including your Windows host, HomeAssistant server, and your router.

Then explain to me how they communicate to each other, VM, VLAN, whatever facilitating that (or in your case, most likely not).

6

4 Port Intel i350 NIC
Windows 11 Pro
Router Ubiquity DR7 - 192.168.1.1

I’m on Windows 11 so I can’t do anything ‘fancy’ with settings inside windows (outside of segmentation), so I have to rely on my router.

Port 1 (Manual Set) - This is the Port I want Nextcloud AIO on.
VMware - VMnet2
UDR7 - 192.168.80.0/24
VLAN80 (UDR7) 192.168.80.153 OR 192.168.1.153

Windows (See Below)

Connection-specific DNS Suffix: 
Description: Intel(R) I350 Gigabit Network Connection
Physical Address: ‎E8-EA-6A-0C-44-B0
DHCP Enabled: No
IPv4 Address: 192.168.80.23
IPv4 Subnet Mask: 255.255.255.0
IPv4 Default Gateway: 
IPv4 DNS Server: 
IPv4 WINS Server: 
NetBIOS over Tcpip Enabled: Yes

Port 2 (DHCP) - Not doing anything with this Port

Windows (See Below)

Connection-specific DNS Suffix: localdomain
Description: Intel(R) I350 Gigabit Network Connection #2
Physical Address: ‎E8-EA-6A-0C-44-B1
DHCP Enabled: Yes
IPv4 Address: 192.168.1.23
IPv4 Subnet Mask: 255.255.255.0
Lease Obtained: Wednesday, January 28, 2026 1:52:03 PM
Lease Expires: Saturday, January 31, 2026 10:32:55 AM
IPv4 Default Gateway: 192.168.1.1
IPv4 DHCP Server: 192.168.1.1
IPv4 DNS Server: 192.168.1.1
IPv4 WINS Server: 
NetBIOS over Tcpip Enabled: Yes

Port 3 (Manual Set) This is the Camera Network
This is VLAN40 (UDR7) and is Isolated from the other networks

Windows (See Below)

Connection-specific DNS Suffix: 
Description: Intel(R) I350 Gigabit Network Connection #3
Physical Address: ‎E8-EA-6A-0C-44-B2
DHCP Enabled: No
IPv4 Address: 192.168.40.23
IPv4 Subnet Mask: 255.255.255.0
IPv4 Default Gateway: 
IPv4 DNS Server: 
IPv4 WINS Server: 
NetBIOS over Tcpip Enabled: Yes

Port 4 (DHCP) - Network the Windows PC runs on
Default VLAN1
Home Assistant - 192.168.1.132

Connection-specific DNS Suffix: localdomain
Description: Intel(R) I350 Gigabit Network Connection #4
Physical Address: ‎E8-EA-6A-0C-44-B3
DHCP Enabled: Yes
IPv4 Address: 192.168.1.26
IPv4 Subnet Mask: 255.255.255.0
Lease Obtained: Wednesday, January 28, 2026 1:52:00 PM
Lease Expires: Saturday, January 31, 2026 10:22:34 AM
IPv4 Default Gateway: 192.168.1.1
IPv4 DHCP Server: 192.168.1.1
IPv4 DNS Server: 192.168.1.1
IPv4 WINS Server: 
NetBIOS over Tcpip Enabled: Yes

So it doesn’t make a difference if I have each (HA & NC) VM NIC Ports on the same VLAN (Default (1)) or on their own respective VLAN (1 & 80). If they are on separate NIC ports (either directly or via VMnet(x) ) Home Assistant Dav or Uptime Kumu will not communicate with Nextcloud.

This confuses me as both are communicating via WAN on 443. Furthermore all other dav / Uptime Robot programs have no problem communicating with Nextcloud. I only see the problem with Home Assistant.

Hopefully you can see the problem?