HA on VMWare No Access After IP address change

Configuration
1

Hi

Pulling my hair out on this as cannot for the life of me work out whats going on.

I Install fresh HA virtualised on my QNAP NAS using the Supervised, haos_ova-14.1.ova file → All is good, and I can restore my backup, and access the config interface via http://192.168.20.122:8123

I visit Settings–>System–>Network, select ‘Static’, and set the IP to 192.168.20.30 (outside my DHCP range)

I hit the Save Button and Wait. Result is that I can never again access my HA

  • No Access on either 192.168.20.30:8123 or the previous IP http://192.168.20.122:8123

  • I can ping the instance on 192.168.20.30

  • I have tried restarting the VM, to no avail

  • I have tried restarting the entire NAS also to no avail

  • I can see that the VM, has been allocated the IP 192.168.20.30

  • If I revert to VM snapshot I took before changing the IP then access returns via http://192.168.20.122:8123

If anyone has any idea what might be causing this, please reply. At the moment I am pretty close to simply giving up!

I can only assume that the IP change has only half-taken effect (ha on one IP, supervisor on another?). Is there a configuration file I can modify prior to rebooting HA to effect the same change?

image
image669×513 16.9 KB

image
image1141×74 8.86 KB

2

Damn… Found the issue

The HA network config setup has auto-set the netmask to 255.255.255.255 eg 192.168.20.30/32 when I selected static and changed my IP. I did not notice it had done this and am frankly astounded that this would be a default behaviour…!

Maybe the browser has auto-filled the 255.255.255.255 although god only knows where it would have gotten it from!

1 Like