Cannot get zima client to connect

hi all,
installed zimaOS (moved from casaos). I had the zima client on a test server and when I built the production server zima client can’t connect to the server, yet i can access the web gui (changed to port 8080) fine.

Not sure if this is related but when I click on the network icon on the top right, i get this:


the ip it shows 172… is not the servers ip whcih is 10.0.22.99

If i go to the cli and type nmcli con show is get
NAME UUID TYPE DEVICE
ZimaCube-eth0 c634ee4a-e0b2-463e-81f9-06de4a00cd6b ethernet eth0
ztd2nlhb6b a19395d8-c521-4d4e-91e6-e5dbd26c9612 tun ztd2nlhb6b
br-2b69a53b5a27 6f1c498a-4048-4581-bafd-850d4e4a3d0d bridge br-2b69a53b5a27
docker0 d9ed2753-aebd-4eda-934e-f1fe45b83984 bridge docker0
lo ddec7f4c-f289-4292-866d-c6ad5ecfcc12 loopback lo
virbr0 00bd7b0c-e603-4577-9d6f-d1a79e07f9e2 bridge virbr0
ZimaCube-eth1 ec9ebbeb-fa9e-4c9c-a107-c66cbe14b88e ethernet –

what am i missing?

I did change the interfaces earlier. could this be the problem that zima server is not listening on the proper interface for connections? How can I check that?

root@ZimaOS:~# netstat -t4lnp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:48237 0.0.0.0:* LISTEN 1240/rpc.mountd
tcp 0 0 127.0.0.1:46053 0.0.0.0:* LISTEN 1471/zimaos-mod-man
tcp 0 0 0.0.0.0:9993 0.0.0.0:* LISTEN 9371/zerotier-one
tcp 0 0 127.0.0.1:42615 0.0.0.0:* LISTEN 1569/icewhale-files
tcp 0 0 127.0.0.1:42043 0.0.0.0:* LISTEN 1573/zimaos
tcp 0 0 0.0.0.0:7681 0.0.0.0:* LISTEN 1047/ttyd
tcp 0 0 0.0.0.0:8181 0.0.0.0:* LISTEN 2220/docker-proxy
tcp 0 0 0.0.0.0:40121 0.0.0.0:* LISTEN 1569/icewhale-files
tcp 0 0 127.0.0.1:39935 0.0.0.0:* LISTEN 1570/zimaos-local-s
tcp 0 0 127.0.0.1:39647 0.0.0.0:* LISTEN 1572/zimaos-virt-ma
tcp 0 0 127.0.0.1:38315 0.0.0.0:* LISTEN 1566/casaos-install
tcp 0 0 127.0.0.1:38325 0.0.0.0:* LISTEN 1628/zimaos-user
tcp 0 0 0.0.0.0:5355 0.0.0.0:* LISTEN 1416/wsdd2
tcp 0 0 0.0.0.0:5355 0.0.0.0:* LISTEN 1416/wsdd2
tcp 0 0 0.0.0.0:5355 0.0.0.0:* LISTEN 1416/wsdd2
tcp 0 0 127.0.0.1:37927 0.0.0.0:* LISTEN 2958/zimaos-app-man
tcp 0 0 0.0.0.0:3702 0.0.0.0:* LISTEN 1416/wsdd2
tcp 0 0 0.0.0.0:3702 0.0.0.0:* LISTEN 1416/wsdd2
tcp 0 0 0.0.0.0:3702 0.0.0.0:* LISTEN 1416/wsdd2
tcp 0 0 0.0.0.0:35807 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:2049 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:2222 0.0.0.0:* LISTEN 2543/ttyd
tcp 0 0 0.0.0.0:35261 0.0.0.0:* LISTEN 1240/rpc.mountd
tcp 0 0 0.0.0.0:1910 0.0.0.0:* LISTEN 1239/ssdpd
tcp 0 0 127.0.0.1:34373 0.0.0.0:* LISTEN 1078/zimaos-gateway
tcp 0 0 0.0.0.0:51003 0.0.0.0:* LISTEN 1240/rpc.mountd
tcp 0 0 127.0.0.1:33637 0.0.0.0:* LISTEN 1530/zimaos-message
tcp 0 0 0.0.0.0:50137 0.0.0.0:* LISTEN 1242/rpc.statd
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 2224/docker-proxy
tcp 0 0 0.0.0.0:81 0.0.0.0:* LISTEN 2267/docker-proxy
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1/systemd
tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 1386/smbd
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 2297/docker-proxy
tcp 0 0 127.0.0.1:32991 0.0.0.0:* LISTEN 1568/icewhale-files
tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 1386/smbd

Hi, would you please provide us with the specs of your machine and the version of the OS?

Zima is running on a BreqWatr vm environement. Latest version 1.4.1
I think i know what the issue may be. does the client connecting and the server need to be on the same network (same vlan)?

At first, they need to be on the same LAN.

And, you need to ensure there is no firewall(on the router) that may block the connection.

Y’a they are on 2 different vlans, but wide open between the 2