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?
