I finally took the time to setup teddycloud on my QNAP NAS using docker.
I backed my cc3200 toniebox up and flashed the c2.der. However, I always get codeword owl.
I also deleted the certificates and let them to be recreated and moving over via uar again but still no changes.
I tried wit only altCA.305 activated (always), with additionally altUrl.305 or altURl.custom.305 (where I put the ip of how I connect. to teddycloud). nothing canges. If I change to ofw1, it connects to boxine as the freshnesscheck.does not create an error code.
I cannot find the box in teddycloud.
Do you have any ideas?
More details please. Used docker compose etc.
Have you set up a separate ip for teddycloud?
I assume the nas is using the 443 port by itself.
Hi Henryk,
Thank you very much for your questions - that already helped me to think about it and try a few more things.
I setup using docker compose with a originally port forwarding/mapping of 443 - but by now I understood that the tonie box cannot handle a different port. And yes, some Apache service is listening on that port and killing it just restarts it (ideally, I do not mess with that).
So then I switched to using macvlan and using a different IP: 192.168.0.99 and also entered that IP to AltUrl.custom.305.json and load that in ofw3.
Still no change - other than the tonieCloud is now accessible on new IP (so I think that setup of macvlan worked).
I am currently on the move (so all above from memory) but was thinking to reply now so that you can ask for a few more things that I should run later and show you the output.
Thank you very much!
The toniebox can reach the teddycloud up? At least it’s not the „normal“ ip range used by default.
Can you reach teddycloud from any other device within your WiFi? What happens if you call [tc-ip]:443 ?