Codeword "Owl". Did nothing, but

Recently I did a fresh tc-server setup. I had a hard time getting the box ←> tc-server connection going. With the help of the telegram channel I finally solved it. Copied certificates over and over and … until someone pointed me to the fritzbox-dns requirements for the servername (“tc”). Changed that and everything was working again.

Yesterday I just replaced the batterypack with a new one and noticed, I’m back at codeword “owl” again. Server-name is correct. IP shouldn’t have changed either (checked “always use same ip” in fritbox settings).

There is juusst one minor thing I did to my internal network in the mean time. But as far as I’m aware, this should not interfere with tc. But maybe you know better:
I set up an nginx-proxy-manager for external https-access for another project (different internal ip). During the process I disabled and reenabled IPV6 support on the fritz!box. Requested several new external IPs. But as far as I’m aware everything should now be the same to before I started.

If the nginx-thingi isn’t the culprit. What else could cause a working TC-setup to throw “owl” again?

The Toniebox needs the 443 port to connect - is is still free or now used by nginx?

nginx sits on port 443 of the external ip. Do I need the internet-ip for the toniebox communication? In my internal network teddycloud and nginx are on different IPs and don’t block each other

disable the changed things and test if it works again. if so, then you broke it with th nginx setup, if not… weird.

Disabled nginx, and external port forwarding.
Restarted tc. Server is available as “tc” in the local network. Port 80, 443, 8443 are reachable.

The Box was seen by tc for a short time (green online symbol) but went offline again, when I did the freshness-check (‘owl’). And does not update, when I play tonies.

grafik

I attached the docker-log file.

log.txt (489.9 KB)

Sounds for me like a wrong ca der on your box.

Please update teddycloud also to latest version which was released today.

Still no success.

Set up a new 0.6.5 tc server. Set hostname to “tc” on the fritzbox. I even reflashed the ca.der from the server path twice.

2025-12-08 20:55:30,104 -- Connecting to target...
2025-12-08 20:55:32,461 -- timed out while waiting for ack
2025-12-08 20:55:32,715 -- Connected, reading version...
2025-12-08 20:55:32,716 -- connected to target
2025-12-08 20:55:32,716 -- Version: CC3x00VersionInfo((0, 4, 1, 2), (0, 0, 0, 0), (0, 0, 0, 0), (0, 0, 0, 0), (16, 0, 0, 0))
2025-12-08 20:55:32,716 -- This is a CC3200 device
2025-12-08 20:55:32,716 -- Switching to NWP bootloader...
2025-12-08 20:55:32,717 -- Switching UART to APPS...
2025-12-08 20:55:32,717 -- Resetting communications ...
2025-12-08 20:55:33,973 -- Uploading rbtl3100s.dll...
2025-12-08 20:55:33,973 -- Reading rbtl3100s.dll from file /home/timo/Dokumente/Toniebox/cc3200tool/cc3200tool/dll/rbtl3100s.dll
2025-12-08 20:55:33,973 -- Getting storage list...
2025-12-08 20:55:34,807 -- APPS version: CC3x00VersionInfo((0, 4, 0, 2), (0, 0, 0, 0), (0, 0, 0, 0), (0, 0, 0, 0), (16, 0, 0, 0))
2025-12-08 20:55:34,809 -- File exists on target, erasing
2025-12-08 20:55:34,810 -- Erasing file /cert/c2.der...
2025-12-08 20:55:34,975 -- Uploading file ca.der -> /cert/c2.der [1317, disk=1317]...
.
2025-12-08 20:55:35,241 -- Read file after writing for verification...
2025-12-08 20:55:35,243 -- Reading file /cert/c2.der -> /tmp/tmp7fydlqc3
2025-12-08 20:55:35,266 -- File /cert/c2.der verified
2025-12-08 20:55:35,266 -- Getting storage info...
2025-12-08 20:55:35,266 -- storage #2 info bytes: 0x10, 0x0, 0x4, 0x0, 0x0, 0x0, 0x0, 0x0
2025-12-08 20:55:35,266 -- Getting storage list...
2025-12-08 20:55:35,267 -- Reading raw storage #2 start 0x0, size 0x2000...
..
2025-12-08 20:55:35,363 -- [1] detected a valid FAT revision: 93
2025-12-08 20:55:35,363 -- Getting storage list...
2025-12-08 20:55:35,363 -- Reading raw storage #2 start 0x1774, size 0x2774...
...
2025-12-08 20:55:35,482 -- selected FAT revision: 93 (active)
2025-12-08 20:55:35,482 -- FAT r93, num files: 27, used/free blocks: 932/92
2025-12-08 20:55:35,482 -- All commands done, bye.

Still codeword owl. Attached is the new docker log. I pulled it right after the last freshness attempt. But I can’t see anything. Is there any other log I could provide?

Also I provided my ngCfg in case i screwed up here. But I didn’t change anything there compared to the last working solution.

ngCfg.json.txt (2.2 KB)

log(3).txt (27.3 KB)

can you post the tc patch? and the altca patch?

no custom dns server in use? Anything like that?

There were some cases where renaming tc to td helped. (dont forget to adapt the tc patch accordingly if you try that)

1 Like

tc Patch:

{
    "general": {
        "_desc": "Changes Boxine URLs to tc.fritz.box.",
        "_memPos": "",
        "_fwVer": "3.0.5+"
    },
    "searchAndReplace": [{
        "_desc": "prod.de.tbs.toys to tc.fritz.box",
        "search":  ["70", "72", "6f", "64", "2e", "64", "65", "2e", "74", "62", "73", "2e", "74", "6f", "79", "73", "00"],
        "replace": ["74", "63", "2e", "66", "72", "69", "74", "7a", "2e", "62", "6f", "78", "00", "??", "??", "??", "??"]
    }, {
        "_desc": "rtnl.bxcl.de to tc.fritz.box",
        "search":  ["72", "74", "6e", "6c", "2e", "62", "78", "63", "6c", "2e", "64", "65", "00"],
        "replace": ["74", "63", "2e", "66", "72", "69", "74", "7a", "2e", "62", "6f", "78", "00"]
    }]
}

AltCA Patch:

{
    "general": {
        "_desc": "Change CA from /cert/ca.der to /cert/c2.der",
        "_memPos": "",
        "_fwVer": "3.0.5+"
    },
    "searchAndReplace": [{
        "_desc": "ca.der to c2.der",
        "search":  ["2f", "63", "65", "72", "74", "2f", "63", "61", "2e", "64", "65", "72", "00"],
        "replace": ["??", "??", "??", "??", "??", "??", "??", "32", "??", "??", "??", "??", "??"]
    }]
}

I have no alternative DNS-server in use. And I can reach tc from the browser under its name “tc/web” just fine.

I’d love to try the tc→td solution. What would I have to change for that to work?

Yay, figured out how to change from tc → td and now it is working again. Thanks for this unexpected solution!

This leads me to the question: WTF? Why would renaming matter? Is this something a Tonie-FW update introduced to prevent usage of tc?

it seems like fritzbox did something that prevents using tc… wiki and patch should be updated sometimes..

Was teddyCloud available via tc.fritz.box? Did it open something different? If it ends up in an error message, what error message?
What does a nslookup does on that domain?

tc.fritz.box opened up just fine. No obvious issues. Because it’s working now with td, I’d rather not revert back to check the exact redirect-address when using “TC"