Issue with TeddyCloud After Flashing Firmware

Description:

I am experiencing issues after flashing my TeddyCloud box. I forgot to update the firmware before flashing, but I do have a backup and patched firmware available. When I power up the box, I hear the codeword sound “Murmeltier.” The box has an IP address on the Wi-Fi network, is pingable, and is displayed as “online” in TeddyCloud.

Actions performed:

  1. Flashed the box without updating the firmware first.

  2. Powered on the box and confirmed the “Murmeltier” sound played.

  3. Verified that the box is connected to the Wi-Fi, has an IP address, and is pingable.

  4. Confirmed that the box shows as “online” in TeddyCloud.

Expected outcome:

The box should function normally after flashing, allowing me to use all its features.

Actual outcome:

Although the box is online and pingable, it is not functioning as expected, and I cannot proceed further.

Environment details:

TeddyCloud version: v0.6.2 (203f12d)

OS: Ubuntu Linux x86_64 (64-bit), running in a Docker environment

Date/Time: 2024-10-26, 18:14:34 +0000

Logs:

I tried to attach the logs captured during this process (teddycloud_logs.txt), but new users can not upload attachments. Relevant sections of the logs include warnings about the client CA not matching Boxine and runtime errors, such as src/cache.c:194:35: runtime error: left shift of 183 by 24 places cannot be represented in type ‘int’.

Steps I’ve taken to resolve the issue:

  1. Restarted the box.

  2. Verified the connection by pinging the box and confirming its “online” status in TeddyCloud.

  3. Attempted to review the logs for more details.

Request:

Could you please provide guidance on how to resolve this issue? Should I re-flash the firmware, or is there a way to recover functionality using the backup and patched firmware?

Flash the original backup, let the box do its firmware update and then start again with teddycloud.

You can use the gui for flashing the backup. Just skip the patch step (click next directly, not patch).

The mentioned warnings in the logs are ok.