Since I only have Teddycloud running on the NAS so far, macvlan is not yet installed—so nothing is interfering with the port. However, applications are now to follow, so that was planned anyway.
I think it would make sense to set up macvlan first so that I can assign the IP/port permanently?
I have a NAS from UGREEN, which has port 443 available. At least as long as the applications don’t interfere with each other 
Everything had been working fine until I reconfigured the Fritzbox.
Then do the macvlan stuff. Note the ip and do the flashing
Since the box has to be up and running next Monday, I haven’t implemented MacVlan yet. Instead, I flashed the box with the new IP of the TC (and the current network data, just to be on the safe side).
TC is online and usable, Boxine is online, the box is also displayed as online in the Fritzbox and TC (but the display for the status/-time is delayed?) – but I still get the code word “Eule/Owl” when I try to refresh or load a new Tonie…
What have I missed now? Toniebox and TC now have permanently assigned IPs in the Fritzbox, which I will then transfer to MacVlan later or reset as soon as I set it up.
In addition, the box no longer starts when the battery is connected? Without the battery, it starts via the charging station, but with the battery, nothing happens. During flashing, it still worked normally with the battery, but then it wouldn’t turn on anymore…
Actually, the battery was fully charged before flashing; I took the box directly from the charging station, where it had been for over 24 hours. So the charging capacity can’t really have been so low during the procedure that it no longer starts up—or can it?
All cable connections etc. look fine, and I didn’t accidentally pull on them or anything like that while flashing or installing/removing them.
Edit:
No entry for failures in the TC/Portainer logs…
Battery problem fixed. I placed the box on the charging station without the battery plugged in and just then reconnected the battery—now it works as usual again (but is charging until tomorrow to be on the safe side).
The owl stays.
You might post the docker logs when doing the the freshness check
online status uses the rtnl functionality iirc and the other things the boxine api. So normally if one is working the other should too.
The freshness check doesn’t even arrive in TC/Docker – there’s no log of anything… 
This is the log from starting TC:
INFO |server.c:0931:server_init| 1 open HTTPS Web connections
INFO |server.c:0931:server_init| 2 open HTTPS Web connections
INFO |server.c:0931:server_init| 6 open HTTPS Web connections
INFO |handler_cloud.c:0041:handleCloudTime| >> respond with current time
INFO |mqtt.c:0690:mqtt_init_box| Skipping client 'Toniebox' (cn: 'default')
INFO |handler_cloud.c:0041:handleCloudTime| >> respond with current time
INFO |mqtt.c:0690:mqtt_init_box| Skipping client 'Toniebox' (cn: 'default')
INFO |cloud_request.c:0200:web_request| Connecting to HTTP server prod.de.tbs.toys:443...
INFO |cloud_request.c:0252:web_request| trying IP: 3.74.99.150
INFO |server.c:0931:server_init| 5 open HTTPS Web connections
INFO |cloud_request.c:0486:web_request| Response: '1764502494'
INFO |cloud_request.c:0200:web_request| Connecting to HTTP server prod.de.tbs.toys:443...
INFO |cloud_request.c:0252:web_request| trying IP: 3.74.99.150
INFO |cloud_request.c:0486:web_request| Response: '1764502495'
INFO |server.c:0931:server_init| 0 open HTTPS Web connections
I’m still getting the owl. Does anyone else have any idea what the problem might be?
The connection attempt doesn’t seem to be reaching the Docker log at all, as there is no entry about it there.
I flashed the Toniebox with the latest data (and Wi-Fi), and attempts to create a new Wi-Fi network using the instructions on the Tonies website also didn’t work.
Switching to offline mode and back didn’t help either.
@henryk
Could that possibly be a solution to my problem with the current owl? So, restore the original backup and then set up a new Wi-Fi connection, as specified on the Tonies website?
But there is no data on IPs etc. on this backup, it’s “empty” in that regard.
https://forum.revvox.de/t/changed-teddycloud-ip-esp32-can-not-connect-anymore-codewort-ant/1059
i am out of ideas. using the tonies way to setup a new wifi should work in all cases.
Didn’t help. But I solved it now:
Apparently, it was the certificates and their assignment on the box, despite the lack of information in the log. I patched the original version without Teddycloud onto the box again, updated it once, then patched the version for Teddycloud again and reinstalled the certificates—now it works as before.
Even though it’s now trying to re-download the custom content, even though it is already on the box, for whatever reason…
Edit:
The problem with re-downloading the custom tags has also been solved:
When I place the tags on the box for the first time, it flashes blue and apparently starts downloading them. If I simply remove them during this process and cancel the operation, they light up green as normal when I place them back on the box.