Upcoming Release 0.6.5

henryk · March 15, 2025, 12:15pm

Changes

Stabilization backend
Fixed error activating RTNL when using TeddyCloud behind a reverse proxy Unable to Activate RTNL in the browser · Issue #291 · toniebox-reverse-engineering/teddycloud · GitHub
gui: Added tonieboxes tab to homepage, user can now choose if he want to see his tonies or tonieboxes. Setting is stored locally.
gui: Some refactoring

Contributors:

And a big Thank you for all bug reports in the time inbetween.

Feel free to have a look onto it and if you see any bug… please report it!

Known bugs:

The Macvendor.com api call is currently not working if no allow CORS browser plugin is used, so please use it directly
There is still a deadlock in rare situations. As this is very rare, it will be fixed in a future version.

Magician · March 20, 2025, 8:34pm

Which is the dead lock GitHub issue id? Does the deadlock occur when starting teddycloud? Sometimes i also see this while one core of the CPU runs at 100% and the logs are empty.

0xbadbee · March 21, 2025, 7:51am

github.com/toniebox-reverse-engineering/teddycloud

TeddyCloud Service Fails to Start Sporadically After System Reboot

opened 09:57AM - 17 Feb 25 UTC

XerXes777

bug

**Describe the bug** After a system reboot, the TeddyCloud service does not star…t correctly sporadically. While the LXC container and the Docker container appear to be running, TeddyCloud is inaccessible via the browser. Additionally, the CPU load in Proxmox increases to ~20%. A manual restart of the LXC container resolves the issue. This issue was only noticed because the system needs to restart regularly due to the scheduled backup process. **To Reproduce** Steps to reproduce the behavior: 1. Reboot the Proxmox host or restart the LXC container. 2. The LXC container starts, and Docker reports that TeddyCloud is running. 3. Attempt to access TeddyCloud via the browser. 4. TeddyCloud is inaccessible. 5. Observe that CPU load in Proxmox increases to ~20%. 6. Restart the LXC container manually. 7. TeddyCloud becomes accessible again. **Expected behavior** TeddyCloud should start correctly and be accessible after a system reboot or container restart, without requiring manual intervention. **Screenshots** N/A **Technical Details:** - TeddyCloud Version: v0.6.3 - Proxmox PVE Version: 8.3.3 - Proxmox Backup Server (PBS) Version: 3.3.2 - LXC Container: Docker LXC (Installed via HelperScript) - Docker Version: 27.4.1 - Docker image used: ghcr.io/toniebox-reverse-engineering/teddycloud:lates **Attach logs of teddyCloud** [_teddycloud_logs (8).txt](https://github.com/user-attachments/files/18823327/_teddycloud_logs.8.txt) **Additional context** - The issue is not caused by the Proxmox backup process itself. - The backup is scheduled for 08:00 AM, but logs show a 1-hour offset (logged at 07:00 AM). - The problem occurs sporadically after a system reboot. - The issue was only noticed because the system needs to restart regularly due to the scheduled backup process.