Error updating to System 0.2.3 from 0.2.2

[carlosroman]

Every time I try and run an update the JetKVM gets to about ~9% of the download and then errors with the following:

Error details: Error downloading system update: error reading response body: context deadline exceeded (Client.Timeout or context cancellation while reading body)

I tried leaving it over night with "Auto Update" enabled but the system still refuses to update.

The current version I have installed is:

App: 0.3.7
System 0.2.2

[ym]

The issue should be resolved. Could you please confirm if you’re still experiencing any problems?

[carlosroman]

I manage to get it to update the App to 0.3.8 but still getting:

An error occurred while updating your device. Please try again later.

Error details: Error downloading system update: error reading response body: context deadline exceeded (Client.Timeout or context cancellation while reading body)

So it still refusing to upgrade the System to 0.2.3. Then again, noticed that there is no release 0.2.3 here. Should we expect there to be one there?

[ym]

Please SSH into your device (can also use Web Terminal) and run the following commands:

ifconfig
ping update.jetkvm.com
wget -O- ip.sb

After running these commands, please send the complete outputs to siyuan+gh258@buildjet.com. This will help us diagnose the issue more effectively.

[eshirvana]

@ym i have the same issue, can;t check for update nor it gets updated :

/ # uname -a 
Linux JetKVM 5.10.160 #1 Tue Feb 18 18:37:50 CET 2025 armv7l GNU/Linux

/ # ifconfig
eth0      Link encap:Ethernet  HWaddr XX:XX:XX:XX:XX
          inet addr:192.168.2.196  Bcast:192.168.2.255  Mask:255.255.255.0
          inet6 addr: fdfe:70e8:9b67:f544:46b7:d0ff:fee6:9d4d/64 Scope:Global
          inet6 addr: fe80::46b7:d0ff:fee6:9d4d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:271167 errors:0 dropped:269 overruns:0 frame:0
          TX packets:4002855 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:66169768 (63.1 MiB)  TX bytes:3226501623 (3.0 GiB)
          Interrupt:53 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:192 errors:0 dropped:0 overruns:0 frame:0
          TX packets:192 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:19200 (18.7 KiB)  TX bytes:19200 (18.7 KiB)

/ # ping update.jetkvm.com
PING update.jetkvm.com (15.235.54.226): 56 data bytes
64 bytes from 15.235.54.226: seq=0 ttl=49 time=6.720 ms
64 bytes from 15.235.54.226: seq=1 ttl=49 time=5.548 ms
64 bytes from 15.235.54.226: seq=2 ttl=49 time=5.427 ms
^C
--- update.jetkvm.com ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 5.427/5.898/6.720 ms

/ # wget -O- ip.sb
Connecting to ip.sb (172.67.75.172:80)
writing to stdout
[p ip]
-                    100% |********************************|    14  0:00:00 ETA
written to stdout

/ # 

[ym]

I've identified the cause and will be preparing a PR this week to fix it, it may fail if the total download time exceeds 1 minute.

[eshirvana]

@ym I was able to see new version available and it seems like it got updated but now as soon as I open jetkvm root page I am welcomed with this message : Failed to get device version

and in the setting :

and clicking on update bottom :

and now I get this error message when click on check for updates:

Error details: Error checking for updates: error checking for updates: error sending request: Get "https://api.jetkvm.com/releases?deviceId=xxxxxxxxxxxxxxx&prerelease=false": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2021-01-02T03:29:03Z is before 2025-02-05T19:18:36Z

[carlosroman]

Wanted to add that after updating the App to 0.3.9 I was able to successfully upgrade the System to 0.2.3.

[stefanvaduva]

It seems that some of us still can't update. Is there anything special that we need to do? No app/system version displayed.

I can ping update.jetkvm.com without any issues from my web terminal

[dropwhile]

I had an issue where the time on my jetkvm was quite far behind (I have ntp servers pushed via dhcp, so not sure why this is the case). This caused tls errors due to the certificates presented as part of tls negotiation being outside acceptable times (eg. cert NOT_BEFORE values).

I was able to enable developer mode and ssh into the unit (web console likely would also work), and use busybox to set the time.

busybox date -s 2025.05.20-21:14:43

Now I'm able to check for updates again.

NOTE: I discovered the tls errors by looking at /data/jetkvm/last.log, and then realized my jetkvm system time was quite far away from an appropriate value (several years off)

[eshirvana]

@dropwhile I think you are right , that's exactly the problem. also the date gets reset after each reboot.
here is the the last.log everytime i restart my jetkvm :

2021-01-01T12:00:19Z WRN jetkvm timesync failed to query NTP server error="lookup time.apple.com on [::1]:53: read udp [::1]:56557->[::1]:53: read: connection refused" server=time.apple.com
2021-01-01T12:00:19Z WRN jetkvm timesync failed to query NTP server error="lookup time.windows.com on [::1]:53: read udp [::1]:43697->[::1]:53: read: connection refused" server=time.windows.com
2021-01-01T12:00:19Z WRN jetkvm timesync failed to query NTP server error="lookup 1.pool.ntp.org on [::1]:53: read udp [::1]:45470->[::1]:53: read: connection refused" server=1.pool.ntp.org
2021-01-01T12:00:19Z WRN jetkvm timesync failed to query NTP server error="lookup time.google.com on [::1]:53: read udp [::1]:39088->[::1]:53: read: connection refused" server=time.google.com
2021-01-01T12:00:19Z WRN jetkvm timesync failed to query NTP server error="dial udp 162.159.200.123:123: connect: network is unreachable" server=162.159.200.123
2021-01-01T12:00:19Z WRN jetkvm timesync failed to query NTP server error="dial udp [2606:4700:f1::123]:123: connect: network is unreachable" server=2606:4700:f1::123
2021-01-01T12:00:19Z WRN jetkvm timesync failed to query NTP server error="lookup 3.pool.ntp.org on [::1]:53: read udp [::1]:48126->[::1]:53: read: connection refused" server=3.pool.ntp.org
2021-01-01T12:00:19Z WRN jetkvm timesync failed to query NTP server error="lookup 2.pool.ntp.org on [::1]:53: read udp [::1]:38386->[::1]:53: read: connection refused" server=2.pool.ntp.org
2021-01-01T12:00:19Z WRN jetkvm timesync failed to query NTP server error="lookup time.aws.com on [::1]:53: read udp [::1]:52381->[::1]:53: read: connection refused" server=time.aws.com
2021-01-01T12:00:19Z WRN jetkvm timesync failed to query NTP server error="lookup 0.pool.ntp.org on [::1]:53: read udp [::1]:58921->[::1]:53: read: connection refused" server=0.pool.ntp.org
2021-01-01T12:00:19Z WRN jetkvm timesync failed to query HTTP server error="Get \"http://www.gstatic.com/generate_204\": dial tcp: lookup www.gstatic.com on [::1]:53: read udp [::1]:43038->[::1]:53: read: connection refused" http_url=http://www.gstatic.com/generate_204 status=0
2021-01-01T12:00:19Z WRN jetkvm timesync failed to query HTTP server error="Get \"http://edge-http.microsoft.com/captiveportal/generate_204\": dial tcp: lookup edge-http.microsoft.com on [::1]:53: read udp [::1]:42812->[::1]:53: read: connection refused" http_url=http://edge-http.microsoft.com/captiveportal/generate_204 status=0
2021-01-01T12:00:19Z WRN jetkvm timesync failed to query HTTP server error="Get \"http://cp.cloudflare.com/\": dial tcp: lookup cp.cloudflare.com on [::1]:53: read udp [::1]:38701->[::1]:53: read: connection refused" http_url=http://cp.cloudflare.com/ status=0

[stefanvaduva]

Thanks, but my date and time seem to be correct. This is the output of /data/jetkvm/last.log