glacial void
I recently setup a new server box, and I want to monitor my NUT server for changes using HA.
It's not working - getting a Connection error: [Errno 113] Connect call failed ('192.168.xxx.xxx', 3493) error.
Anyone know how I can fix this? On my old HA server I want to decommission it is still working just fine, along with other web apps I have that monitor the UPS.
Will mark as resolved when fixed! 🙂
digital ibex
I recently setup a new server box, and I want to monitor my NUT server for chang...
I believe that by default the port is not exposed externally
glacial void
Any other ideas? I think it's talking to other host machines fine
In all honesty, this new host is closer to the endpoint than the other ones that are able to talk
I also use TrueNAS as the master NUT server and I did check to allow externally
and it made other web apps work on other hosts work just like that
digital ibex
113 is usually "no route to host" do you have vlans set up and there is a configuration issue?
glacial void
yeah that's what I'm not sure about. I'm using Incus as a VM manager to use the qcow2 HAOS image for the first time
Incus is built into truenas which is where the master NUT server is
but other VMs outside of my truenas server (ie. VM on another machine) can access the truenas nut master IP
must be a cfg issue
using the qcow2 file from here (https://www.home-assistant.io/installation/alternative)
not sure if that matters
digital ibex
sounds like there is a configuration somewhere that isolates the vm's
digital ibex
yeah i dont know much about it either
glacial void
currently just implemented in truenas' beta codenamed fangtooth
it's showing quite a lot of potential
digital ibex
you could maybe set up an additional bridge network adaptor on both vm's with static ips on a different subnet then they could directly talk to each other
glacial void
yeh I'll see what I can do. was hoping to have just a simple bridge
normally how I do it, but I do need to have a vlan project happen
digital ibex
maybe ask on truenas support about vm's talking to each other. there might be a trick to do it easily
glacial void
yeah it's definitely some sort of networking relationship issue