I have successfully set up my TeddyCloud using Docker on my QNAP. Flashing and patching also worked, and my Toniebox connects to the TonieCloud without any issues. I have uploaded several custom contents to TeddyCloud and linked them to my own Tonies (RFID tags from RFIDfriend).
Previously, I was able to play a purchased Tonie (Benjamin Blümchen) without any problems. However, saving it to TeddyCloud failed multiple times. Now, I can no longer play any additional purchased Tonies at all.
(Edit: “I just noticed that Benjamin Blümchen is actually working.
The other figures are showing error code ‘Eule’.”)
I have tried everything I could think of (many restarts of the container, TeddyCloud, and the Toniebox). The figures are visible in TeddyCloud, but they only show the RFID ID without a name.
Could someone please try to help me? I can upload log files here—do I need to remove anything sensitive from them before posting?
I hope I posted this in the right place.
Thank you very much for your help, also on behalf of my grandchildren!
Thank you very much for your answers. Of course I already searched for the code word “owl”, but there was nothing that helped me. The cloud is also already enabled and the connection to Boxine is green. I would also like to send log files, but first I wanted to know whether I should delete something there (certificates or any addresses or IDs)?
I look forward to further suggestions from you, thanks in advance
nogrup
Okay, then here comes the log file from my Docker container. I hope it’s okay that I attach it as a text file, I don’t know how it otherwise works with a window like this.
Thanks! TeddyCloud_Logs.txt (33.7 KB)
INFO |cloud_request.c:0200:web_request| Connecting to HTTP server api.revvox.de:443...
ERROR|platform_linux.c:0398:resolve_host| getaddrinfo Temporary failure in name resolution
ERROR|cloud_request.c:0233:web_request| Failed to resolve ipv4 address!
ERROR|toniesJson.c:0244:tonieboxes_update| ... failed updating tonieboxes.json error=Address not found [553]
seems that you have and DNS issue. Check you config/network (DNS server settings). And ensure internet connection for you container including a working name resolution.
First of all, thank you very much, dear OliKo, for this hint. I spent a long time yesterday working on the firewall settings on my QNAP, but even when I temporarily disable it, it still doesn’t work. I also experimented with DNS settings and ports with the help of ChatGPT, but I’m not making any progress. I’ll keep experimenting and first see if I can get a TeddyCloud installation in Portainer on my laptop to run.
A question about this:
I have already patched the Toniebox and downloaded the original firmware. Can I now simply copy the contents of the “certs/clients” folder into the newly created TeddyCloud on the laptop? What else do I need to consider if my Toniebox is already modified? (The name and IP must be the same, of course.) Or do I have to go through the entire flashing process again?
Thank you all so much for your help, and I wish everyone a wonderful Sunday.
nogrup
Thank you for this hint. I would like to try it and recreate my TeddyCloud using the modified docker-compose.yaml file.
However, I am very curious to know whether I can simply copy the certs/client directory from the old TeddyCloud into the newly created one, or if I need to flash the Toniebox again?
yes, you need to use the same certificates. Please make a backup of our client.der and private.der. If you loose them, you are in trouble!
ca.der should also be backed up, but can be revocered using a script, available here.
Unfortunately, I’m still stuck. I have reinstalled Teddycloud and, as suggested, modified the YAML file (adjusted the DNS server to 1.1.1.1) and copied the certificates of the already flashed Toniebox—“private.der”, “client.der”, and “ca.der”—into the _data/client directory.
Teddycloud is accessible, and Boxine shows green.
However, the Toniebox is still not reachable and shows the “Owl” error message.
I’m attaching freshly generated log files again. It would be great if someone could take another look and has an idea of what might be wrong.
Did you back up the server certs? That’s is the most important thing besides same ip/hostname if you want to change teddycloud to another host without need of reflashing.
If you do not have backed them up and copied the files to the new instance, than this is the problem. If you still in possession of the old teddycloud installation, then copy the certs/server files to your new one. That might fix the problem. If not, you have to flash/copy the new generated teddycloud ca certificate to your toniebox (depends on your box version) again.
That’s unfortunate; I’ll have to repeat the flashing process. I didn’t keep the server certificates—I thought only the client ones were important and that the server would retrieve them again from the Toniecloud.
Yiiiipppiiieeeehhhh!
What a stroke of luck! I just found the deleted server certificates in the recycle bin on my QNAP. I copied them back to the directory, and everything worked immediately.
I’m absolutely thrilled! Thank you so much for your amazing project and all the effort you put into it.
You made my day, better my week or month.
