The box is still on? Or does the box shutdown/crash after these few seconds?
Why would the router kick the box after granting access? Sounds more like a toniebox related issue.
The box is still on? Or does the box shutdown/crash after these few seconds?
The box is connected, then disappears immediately. Placing the Tonie on the box (which is already saved on the SD card) and it starts playing immediately. So I don’t think it has crashed. When doing the freshnesscheck and placing a tonie on the box, it starts playing. Box appears in router. Box is telling me “Ant” and music starts again.
So I have now flashed back the original version. And tried to connect to the WLAN (mobile hotspot) there, but have the same problem (ant). And I no longer know what to do.
To make it even easier and less error-prone, I have renamed the hotspot and removed the password. And then entered this when changing the Toniebox password. But the error remains the same.
Have you also tried to connect it to your Router instead of the mobile hotspot? Same behaviour?
Tested on a Fritz!Box right now. Same issue.
Tested with a guest network too.
Disabled 5ghz. Still the same.
Fritz!Box output for the toniebox: Last connection 23.11.2024, 13:51
Another thought came to my mind: Is it possible that WIFI is fried if the box is able to connect (for a short while)? Fried = not working? (would be my assumption)
Or could the connection problem be caused if not the right “backup”/original firmeware was flashed back on the box?
In case anyone is experiencing the same problem:
I used the wrong file to flash back the original Toniebox firmware.
Luckily I found another backup - with this one the wifi connects again (if using the original toniebox firmeware).
When flashing again, the problem still exists and I wifi can’t connect.
I will look into this again tomorrow.
Update: I flashed the original firmeware again - and wifi is working (tested with a creative tonie, changed songs on it and box is playing the new ones)
Following some hints from the telegram channel. If you are jonas, then nothing new for you 
The mentioned ip 172.19…:
It sounds like the internal docker ip. Not the right ip.
Is teddycloud reachable from all devices in your network with this ip? What is the internal ip of your computer in your network? ( cmd → ipconfig /all ) Is this the ip shown in your FRITZ!box for the teddycloud server?
Can you also post your docker-compose.yaml ? Check if the ports are not outcommented with #