Failed to de-register device #325

New issue

Closed

opened 2026-02-20 08:21:59 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-20 08:21:59 -05:00

Owner

Originally created by @rherring on GitHub (Jun 13, 2025).

Back in March, I was having issues connecting to my device via the cloud. After MANY attempts, I reluctantly gave in and "de-registered" my device from the cloud, where I was being presented with the option. Since then, I cannot re-register my device. On my JetKVM the only option I have is "De-register from Cloud" which I did back in March. When I click that button, I get this:

Failed to de-register device: failed to send deregister request: Delete "https://api.jetkvm.com/devices/10d4eb58aff3de52": t|s: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2021-01-01112:04:28Z is before 2025-06-04105:54:13Z

Any help would be much appreciated.

Originally created by @rherring on GitHub (Jun 13, 2025). Back in March, I was having issues connecting to my device via the cloud. After MANY attempts, I reluctantly gave in and "de-registered" my device from the cloud, where I was being presented with the option. Since then, I cannot re-register my device. On my JetKVM the only option I have is "De-register from Cloud" which I did back in March. When I click that button, I get this: `Failed to de-register device: failed to send deregister request: Delete "https://api.jetkvm.com/devices/10d4eb58aff3de52": t|s: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2021-01-01112:04:28Z is before 2025-06-04105:54:13Z` Any help would be much appreciated.

deekerman closed this issue

2026-02-20 08:21:59 -05:00

deekerman commented

2026-02-20 08:22:00 -05:00

Author

Owner

@IDisposable commented on GitHub (Jun 13, 2025):

That sounds like your RTC clock isn't setting itself via NTP. Can you control the device enough to get to the Settings/Network page and set the NTP to NTP only (not HTTP or Both)... then after saving power-cycle the JetKVM and it should come back with the clock set.... at which point TLS/HTTPS will work.

@IDisposable commented on GitHub (Jun 13, 2025): That sounds like your RTC clock isn't setting itself via NTP. Can you control the device enough to get to the Settings/Network page and set the NTP to NTP only (not HTTP or Both)... then after saving power-cycle the JetKVM and it should come back with the clock set.... at which point TLS/HTTPS will work.

deekerman commented

2026-02-20 08:22:00 -05:00

Author

Owner

@rherring commented on GitHub (Jun 13, 2025):

How do I go about doing that? There's nothing mentioning the clock on the settings tab.

@rherring commented on GitHub (Jun 13, 2025): How do I go about doing that? There's nothing mentioning the clock on the settings tab.

deekerman commented

2026-02-20 08:22:00 -05:00

Author

Owner

@rherring commented on GitHub (Jun 13, 2025):

Thank you @IDisposable for helping me get to a resolution for this. I was able to use the information found #293 to get my date fixed and "de-register" my device.

@rherring commented on GitHub (Jun 13, 2025): Thank you @IDisposable for helping me get to a resolution for this. I was able to use the information found #293 to get my date fixed and "de-register" my device.