V1.10.0 release 3 firmware causes problem

my RM10’s date goes back to 1970 after upgrading to the latest firmware.

no matter what i do, it got stuck with year 1970.

i can use local access but no more kvm cloud service.

it was runing perfectly fine with previous firmware 1.9.1.

please look into this issue.

export log to us

system_logs_19700101_001521.zip (113.8 KB)

Is it still the same after restarting the device?

If it still doesn't work, please try disabling the cloud service and restarting. See if the time is correct.

i have tried restarting, reset, and reinstallation of the firmware. no luck.

i am not able to disable the cloud service on the device. it won’t toggle off and also my email address disappeared in the cloud service window.

system_logs_20260819_175553.zip (1.3 MB)
logs from other device
It was late several hours

Today I had a problem with two devices RM10, both updated to V1.10.0 release3. Can’t connect to glkvm cloud service AND talscale.

They are in different countries and both shurely was have a stable internet.

system_logs_20260819_135439.zip (680.7 KB)

These two logs do not appear to indicate any time synchronization issues. The network operator or firewall governing the KVM network appears to be interfering with the connection to the cloud platform (https://gslb-eu.goodcloud.xyz).

i don’t have a cloud service icon.

Screenshot 2026-08-19 105531

Do you access it via the app? Try using a browser instead—the app may have blocked this button.

i can only see the devices that are online in the browser. it’s offline due to the wrong date, so i can only use the app the do local access on this unit.

i cannot find such button in a browser from a different device either btw. that means i don’t have this botton on both of the app and browser (i have tried different pcs and get the same results).

access it directly by ip address in browser

it’s greyed out. when i try to bind, it shows the message in the pic. also, the unit got stuck with “checking clould service status…” message.

Try disabling it, then restart. See if the time gets synchronized. I have a slight suspicion that Cloud's own time synchronization code is interfering with the default time sync. After the time synchronization is completed, reopen the cloud.

Or could you allow me to remotely access your computer? PM me a remote access method.

still a no go.