Stuck at accessing ESP32

[Joke]

Ok, with your help I got at least further…
I managed to read the flash:

Then writing wasn’t possible, USB already connected:

After another powercycle I managed to write the patched image and the Box obviously connected to the router:

But I don’t see the Box in the WebUI:

What did I do wrong?
Do I have to change the “TeddyCloud hostname”? I tried “localhost” and “teddycloud” according to my docker-compose.yaml-file:

services:
teddycloud:
container_name: teddycloud
hostname: teddycloud
image: Package teddycloud · GitHub
ports:
- 8080:80 #optional
- 443:443 #Port is needed for the connection for the box
volumes:
- certs:/teddycloud/certs
- config:/teddycloud/config
- content:/teddycloud/data/content
- library:/teddycloud/data/library
- firmware:/teddycloud/data/firmware
restart: unless-stopped
volumes:
certs:
config:
content:
library:
firmware:

[ruN]

thats progress, nice! You have to put the IP or Hostname of the teddycloud server there.

localhost does not reference to teddycloud in the view from your box. So the question is where are you running the teddycloud server? Do a “ip a” (linux) or ipconfig (win) on the machine thats hosting teddycloud. That IP goes to the patched image wich you are writing back to your box.

The idea behind this is your box connects to your teddycloud server und your teddycloud server connects to boxine cloud.

[henryk]

If you hide the Mac you should also hide the filename of your flash image.

You can also use the new gui for the flashing give it a try when you are flashing the correct ip of your teddycloud. There are some more hints to make the process easier.

[Joke]

You’re right!

Sadly when trying to switch to https, I can’t reach the GUI anymore…

[henryk]

You have to switch to port 443

This seems to be a problem on the auto redirect if a port is part of the url. Hm. Currently I do not have an idea how to solve that automatically.

Edit: the used ports can be stored in the settings. The default values are currently 80 and 443. you should adapt that to the used ones. I will use these values for the autoredirect in future.

[Joke]

That worked!
And for the “TeddyCloud Hostname” I just have to put in the IP from my Notebook (10.0.0.72 in my case) without “http://”, right?
Do I have to change something here too:

I don’t get what I’m doing wrong, it just doesn’t connect…

I wanted to try two other PCs, but port 443 is taken on both…

[henryk]

The box appears in your WiFi?

And did you make a freshnesscheck?

Anything in rtnl log or docker log?

[henryk]

I entered the ip of the teddycloud (with http) as hostnamen in teddycloud settings

[Joke]

The box is in the WiFi, yes but I do get an error with the freshnesscheck - “codeword owl”…

[henryk]

Test & Troubleshooting

[henryk]

that’s fixed in the current pr to develop

[Joke]

Hey guys, mind helping me again?
After a vacation I decided to give it another try.
I deleted the whole docker image and started from scratch.
After the first flash with the error “turtle”, I ended up with “codeword owl” again.
I don’t know what to do or solve this error.
The troubleshoot isn’t really helping me…
Could you help me please?

PS.: The toniebox is checked in in the WiFi and the client certificates are in lower cases.

[Joke]

I just checked the log and it says:

INFO |handler_cloud.c:0041:handleCloudTime| >> respond with current time
INFO |mqtt.c:0685:mqtt_init_box| Skipping client ‘Toniebox’ (cn: ‘default’)
INFO |cloud_request.c:0157:web_request| Connecting to HTTP server prod.de.tbs.toys:443…
INFO |cloud_request.c:0207:web_request| trying IP: 18.156.186.144
INFO |cloud_request.c:0033:httpClientTlsInitCallbackBase| Initializing TLS…
INFO |cloud_request.c:0068:httpClientTlsInitCallbackBase| Initializing TLS done
ERROR|cloud_request.c:0217:web_request| Failed to connect to HTTP server! Error=Unknown certificate authority [537]

So I guess it’s Troubleshoot 1.2.3 but I don’t know how to solve this…

[0xbadbee]

You are missing the client certificates or they are broken. Are you using the original CA or you are using the teddycloud CA from a previous flash? You need the original one for the client certificates.

Did you backup your server certificates or did you flash your box again?

[Joke]

I did flash the box again. Does that mean, I bricked it??

[0xbadbee]

If you don’t have the previous backup saved somewhere, you at least lost the Boxine CA. But you are somewhat lucky, as it is the same on all boxes, so you can extract it from another box.

[Joke]

I got some backups, but I don’t know, if I made them of the original image or after patching… How do I find it out?

And if not, would someone be so nice and send me the needed files?

[Joke]

I tried patching and flashing the oldest Backup, but still “codeword owl” - so I guess, I messed up…

Would really be nice, if someone could send me the needed files, because this is our first and only Toniebox.

[0xbadbee]

I would ask for that in the telegram group.