Olares One reachable on LAN but gateway not running (“Network Not Ready” / olares connection error) after working for 5 days

[mistonthemountain0602-blip]

Device: Olares One

The device worked normally for about 5 days after the initial setup. Then it suddenly stopped working and now appears stuck in a "Network Not Ready" state.

Current behavior:

• The device powers on normally (fans running).
• My router detects the device on Wi-Fi.
• The router assigns it an IP address (192.168.0.197).
• I can successfully ping the device from my computer.
• However, the LarePass app cannot detect the device anymore.
• The app previously showed "Network Not Ready".

Manual tests:

• ping 192.168.0.197 works
• curl https://192.168.0.197 fails (connection refused / port 443 closed)
• https://desktop.tylertaro.olares.com returns the page "olares connection error"
• http://olares.local does not resolve

Troubleshooting already tried:

• restarted the Olares device multiple times
• restarted the router
• confirmed the device appears in the router's connected devices list
• confirmed the device responds to ping but no web service responds

Based on these tests the device is reachable on the network, but it looks like the Olares gateway or internal services are not running.

Since the device worked for several days before this happened, I’m not sure what changed.

Is there a recommended way to recover the system or reinstall Olares when the device is reachable via LAN but the services are not responding and LarePass cannot detect it?

[pengpeng]

We’re sorry for the trouble this may be causing.

When you have a moment, could you please SSH into the device at 192.168.0.197 by following this guide?
https://docs.olares.com/one/access-terminal-ssh.html

After logging in, please run:

kubectl get pods -A

This will list all pods across namespaces. Kindly check if any of them are not in the Running state and let us know what you see. We truly appreciate your help in troubleshooting this.

[mistonthemountain0602-blip]

Thank you for the quick reply!

I tried to SSH into the device as requested:

ssh root@192.168.0.197

but the connection times out:

ssh: connect to host 192.168.0.197 port 22: Operation timed out

The device responds to ping (0% packet loss), but port 22 does not open so I cannot log in to run:

kubectl get pods -A

[pengpeng]

The username is olares, and the password is saved in the LarePass Vault. You can refer to this guide for details:
https://docs.olares.com/one/access-terminal-ssh.html

Then connect using:

ssh olares@192.168.0.197

[mistonthemountain0602-blip]

Hi Pengpeng,

The Olares desktop stopped working again and SSH disconnects every few minutes.

I connected through SSH and checked the cluster.

The bfl pod is crashing with this error:

panic: Get "https://10.233.0.1:443/api?timeout=32s": dial tcp 10.233.0.1:443: connect: no route to host

Many pods in kube-system also show "Unknown" status and their IP becomes . It looks like the cluster service network (10.233.0.0/16) routing is broken, possibly related to Calico.

Node name: olares
SSH IP: 192.168.0.197

Here is the command output I captured:
olares@olares:~$ kubectl -n user-space-tylertaro logs bfl-0 --all-containers --tail=200 &&
kubectl -n kube-system get pods -o wide &&
kubectl -n kube-system logs $(kubectl -n kube-system get pods | grep calico-node | awk '{print $1}') --tail=200 &&
kubectl -n kubesphere-system logs $(kubectl -n kubesphere-system get pods | grep ks-apiserver | awk '{print $1}') --tail=200
net.core.somaxconn = 65535
net.ipv4.ip_local_port_range = 1024 65535
net.ipv4.tcp_tw_reuse = 1
fs.file-max = 1048576
panic: Get "https://10.233.0.1:443/api?timeout=32s": dial tcp 10.233.0.1:443: connect: no route to host

goroutine 1 [running]:
bytetrade.io/web3os/bfl/pkg/client/clientset/v1alpha1.init.1.func1()
/workspace/bytetrade.io/web3os/bfl/pkg/client/clientset/v1alpha1/client.go:53 +0x5b
sync.(*Once).doSlow(0xc00042a310?, 0x13dbcaf?)
/usr/local/go/src/sync/once.go:76 +0xb4
sync.(*Once).Do(...)
/usr/local/go/src/sync/once.go:67
bytetrade.io/web3os/bfl/pkg/client/clientset/v1alpha1.init.1()
/workspace/bytetrade.io/web3os/bfl/pkg/client/clientset/v1alpha1/client.go:50 +0x2c
panic: Get "https://10.233.0.1:443/api?timeout=32s": dial tcp 10.233.0.1:443: connect: no route to host

goroutine 1 [running]:
bytetrade.io/web3os/bfl/pkg/client/clientset/v1alpha1.init.1.func1()
/workspace/bytetrade.io/web3os/bfl-ingress/pkg/client/clientset/v1alpha1/client.go:53 +0x5b
sync.(*Once).doSlow(0xc0005ac620?, 0x14214cf?)
/usr/local/go/src/sync/once.go:76 +0xb4
sync.(*Once).Do(...)
/usr/local/go/src/sync/once.go:67
bytetrade.io/web3os/bfl/pkg/client/clientset/v1alpha1.init.1()
/workspace/bytetrade.io/web3os/bfl-ingress/pkg/client/clientset/v1alpha1/client.go:50 +0x2c
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
calico-kube-controllers-7896849f9b-h7q9q 0/1 Unknown 65 (92s ago) 11d olares
coredns-5d64c756b8-hp7rx 1/1 Terminating 0 102s 10.233.98.86 olares
hami-device-plugin-qzldm 2/2 Terminating 0 112s 192.168.0.197 olares
hami-nvidia-dcgm-exporter-msnrz 0/1 Unknown 62 11d olares
hami-scheduler-57465fb654-7rl5j 0/2 Unknown 67 (3m23s ago) 11d olares
hami-webui-7948864f54-mtxwk 0/2 Unknown 66 (3m23s ago) 11d olares
openebs-localpv-provisioner-76547d4f47-xwd48 0/1 Unknown 107 11d olares
error: expected 'logs [-f] [-p] (POD | TYPE/NAME) [-c CONTAINER]'.
POD or TYPE/NAME is a required argument for the logs command
See 'kubectl logs -h' for help and examples

[dkeven]

Hi @mistonthemountain0602-blip , based on the currently observed behavior, the issue may no longer be limited to the Kubernetes layer. It is more likely related to the network or routing configuration at the Linux system level that we have never seen.
Could you please recall whether any network-related configuration changes were made on the Linux system of this device, or whether any software that might affect networking was installed before the issue occurred?
To help us further investigate the problem, please run the sudo olares-cli logs command to collect more detailed logs and send the generated file to hi@olares.com email. Once we receive the logs, we will analyze them and get back to you as soon as possible.
We apologize again for the inconvenience and appreciate your understanding and cooperation.

[mistonthemountain0602-blip]

Thanks for your prompt response and being so helpful.
I ran sudo olares-cli logs and emailed the generated log bundle to hi@olares.com.
Looking forward to getting this resolved.

[dkeven]

Thanks for your prompt response and being so helpful. I ran sudo olares-cli logs and emailed the generated log bundle to hi@olares.com. Looking forward to getting this resolved.

After inspecting the relevant logs, we suspect that the current network issue may be caused by the device connecting to the same router through both wired and wireless networks, combined with certain factors at the ARP layer.
Please try the following steps:
Connect the device using a wired network connection. In this case, just leave the wired network cable connected.
Turn off Wi-Fi by running: sudo nmcli r wifi off on the device.
In LarePass, check whether the device enters the ip-changing state.
Wait for the ip-changing process to finish. If LarePass still cannot retrieve the device status, please wait at least 10 minutes. Do not reboot the device during this time. Once it finishes, please try accessing the system again.