No connection to Boxine, Bad certificate 533

[abandenfels]

I’m having a problem connecting to Boxine. I have no idea how long this has been going on. (since the version upgrade?) I’m sure it was working, because I was able to download several items from the Boxine cloud. I checked the log and saw that a certificate cannot be read or is invalid. (Bad certificate 533) I generated the certificates with the ‘gencert.sh’ tool because I have a CC3235 Toniebox. This is the log when I restart the container and open the teddycloud webpage:

date	stream	content
2026/02/08 20:19:11	stderr	ERROR|handler_reverse.c:0029:handleReverse| cloud_request_get() failed
2026/02/08 20:19:11	stderr	ERROR|cloud_request.c:0262:web_request| Failed to connect to HTTP server! HTTP=Unknown HTTP Status Code error=Bad certificate [533]
2026/02/08 20:19:10	stderr	ERROR|handler_reverse.c:0029:handleReverse| cloud_request_get() failed
2026/02/08 20:19:10	stderr	ERROR|cloud_request.c:0262:web_request| Failed to connect to HTTP server! HTTP=Unknown HTTP Status Code error=Bad certificate [533]
2026/02/08 20:19:09	stderr	ERROR|handler_reverse.c:0029:handleReverse| cloud_request_get() failed
2026/02/08 20:19:09	stderr	ERROR|cloud_request.c:0262:web_request| Failed to connect to HTTP server! HTTP=Unknown HTTP Status Code error=Bad certificate [533]
2026/02/08 20:19:09	stderr	ERROR|handler_reverse.c:0029:handleReverse| cloud_request_get() failed
2026/02/08 20:19:09	stderr	ERROR|cloud_request.c:0262:web_request| Failed to connect to HTTP server! HTTP=Unknown HTTP Status Code error=Bad certificate [533]
2026/02/08 20:19:08	stderr	ERROR|handler_reverse.c:0029:handleReverse| cloud_request_get() failed
2026/02/08 20:19:08	stderr	ERROR|cloud_request.c:0262:web_request| Failed to connect to HTTP server! HTTP=Unknown HTTP Status Code error=Bad certificate [533]
2026/02/08 20:19:08	stderr	ERROR|handler_reverse.c:0029:handleReverse| cloud_request_get() failed
2026/02/08 20:19:08	stderr	ERROR|cloud_request.c:0262:web_request| Failed to connect to HTTP server! HTTP=Unknown HTTP Status Code error=Bad certificate [533]
2026/02/08 20:19:07	stderr	ERROR|handler_reverse.c:0029:handleReverse| cloud_request_get() failed
2026/02/08 20:19:07	stderr	ERROR|cloud_request.c:0262:web_request| Failed to connect to HTTP server! HTTP=Unknown HTTP Status Code error=Bad certificate [533]
2026/02/08 20:19:07	stderr	ERROR|handler_reverse.c:0029:handleReverse| cloud_request_get() failed
2026/02/08 20:19:07	stderr	ERROR|cloud_request.c:0262:web_request| Failed to connect to HTTP server! HTTP=Unknown HTTP Status Code error=Bad certificate [533]
2026/02/08 20:19:06	stderr	ERROR|handler_reverse.c:0029:handleReverse| cloud_request_get() failed
2026/02/08 20:19:06	stderr	ERROR|cloud_request.c:0262:web_request| Failed to connect to HTTP server! HTTP=Unknown HTTP Status Code error=Bad certificate [533]
2026/02/08 20:19:06	stderr	ERROR|handler_reverse.c:0029:handleReverse| cloud_request_get() failed
2026/02/08 20:19:06	stderr	ERROR|cloud_request.c:0262:web_request| Failed to connect to HTTP server! HTTP=Unknown HTTP Status Code error=Bad certificate [533]
2026/02/08 20:19:06	stderr	ERROR|handler_reverse.c:0029:handleReverse| cloud_request_get() failed
2026/02/08 20:19:06	stderr	ERROR|cloud_request.c:0262:web_request| Failed to connect to HTTP server! HTTP=Unknown HTTP Status Code error=Bad certificate [533]
2026/02/08 20:19:06	stderr	ERROR|handler_reverse.c:0029:handleReverse| cloud_request_get() failed
2026/02/08 20:19:06	stderr	ERROR|cloud_request.c:0262:web_request| Failed to connect to HTTP server! HTTP=Unknown HTTP Status Code error=Bad certificate [533]
2026/02/08 20:19:06	stderr	ERROR|handler_reverse.c:0029:handleReverse| cloud_request_get() failed
2026/02/08 20:19:06	stderr	ERROR|cloud_request.c:0262:web_request| Failed to connect to HTTP server! HTTP=Unknown HTTP Status Code error=Bad certificate [533]
2026/02/08 20:19:06	stderr	ERROR|handler_reverse.c:0029:handleReverse| cloud_request_get() failed
2026/02/08 20:19:06	stderr	ERROR|cloud_request.c:0262:web_request| Failed to connect to HTTP server! HTTP=Unknown HTTP Status Code error=Bad certificate [533]
2026/02/08 20:19:06	stderr	ERROR|handler_reverse.c:0029:handleReverse| cloud_request_get() failed
2026/02/08 20:19:06	stderr	ERROR|cloud_request.c:0262:web_request| Failed to connect to HTTP server! HTTP=Unknown HTTP Status Code error=Bad certificate [533]
2026/02/08 20:19:06	stderr	ERROR|handler_reverse.c:0029:handleReverse| cloud_request_get() failed
2026/02/08 20:19:06	stderr	ERROR|cloud_request.c:0262:web_request| Failed to connect to HTTP server! HTTP=Unknown HTTP Status Code error=Bad certificate [533]
2026/02/08 20:19:06	stderr	ERROR|handler_reverse.c:0029:handleReverse| cloud_request_get() failed
2026/02/08 20:19:06	stderr	ERROR|cloud_request.c:0262:web_request| Failed to connect to HTTP server! HTTP=Unknown HTTP Status Code error=Bad certificate [533]
2026/02/08 20:19:06	stderr	ERROR|handler_reverse.c:0029:handleReverse| cloud_request_get() failed
2026/02/08 20:19:06	stderr	ERROR|cloud_request.c:0262:web_request| Failed to connect to HTTP server! HTTP=Unknown HTTP Status Code error=Bad certificate [533]
2026/02/08 20:18:17	stderr	INFO |settings.c:0870:settings_load_ovl| Load settings from /teddycloud/config/config.ini
2026/02/08 20:18:17	stderr	INFO |tls_adapter.c:0201:read_certificate| File '/teddycloud/certs/client/6c302a3a3f8d/private.der' detected as DER style RSA PRIVATE KEY
2026/02/08 20:18:17	stderr	INFO |tls_adapter.c:0197:read_certificate| File '/teddycloud/certs/client/6c302a3a3f8d/client.der' detected as DER style CERTIFICATE
2026/02/08 20:18:17	stderr	INFO |tls_adapter.c:0197:read_certificate| File '/teddycloud/certs/client/6c302a3a3f8d/ca.der' detected as DER style CERTIFICATE
2026/02/08 20:18:17	stderr	INFO |tls_adapter.c:0204:read_certificate| File '/teddycloud/certs/server/teddy-key.pem' assumed PEM style
2026/02/08 20:18:17	stderr	INFO |tls_adapter.c:0204:read_certificate| File '/teddycloud/certs/server/teddy-cert.pem' assumed PEM style
2026/02/08 20:18:16	stderr	INFO |tls_adapter.c:0204:read_certificate| File '/teddycloud/certs/server/ca-key.pem' assumed PEM style
2026/02/08 20:18:16	stderr	INFO |tls_adapter.c:0204:read_certificate| File '/teddycloud/certs/server/ca-root.pem' assumed PEM style
2026/02/08 20:18:16	stderr	INFO |settings.c:0870:settings_load_ovl| Load settings from /teddycloud/config/config.overlay.ini
2026/02/08 20:18:16	stderr	
2026/02/08 20:18:16	stderr	TeddyCloud v0.6.5 (6682b48) - 2025-12-06 10:13:56 +0100 ubuntu linux-x86_64(64)
2026/02/08 20:18:16	stdout	Running teddycloud...

Does anyone have any idea which certificate this is?
Does anyone have any idea how I could solve this issue?

[0xbadbee]

Check the log on boot.
Your Boxine cert is most likely wrong or broken. This has nothing to do with your server certs

[abandenfels]

Thanks for your replay.

I could solve the issue. It was a DNS problem. My docker host system should not use my local dns server. Since I have a cc3235 Toniebox I had to change the DNS for prod.de.tbs.toys and rtnl.bxcl.de. But this should only affect the toniebox. In my case teddycloud was also redirected for prod.de.tbs.toys and rtnl.bxcl.de and this was wrong. (I’m an idiot ) The question why it was working until a restart of the docker host system is, because my dns configurations were not applied until this restart.

If you are facing a similar issue, where a connection to boxine is not possible, then read this introduction:

Teddycloud CC3235 Newbie HowTo

Hi there, within this post I try to make a documentation how to set up Teddycloud on a CC3235 Box. Read the official documentation as well Proceed at your own risk (which is quite low) Intro Only two weeks ago I bought my first Toniebox ever with the goal to patch it and run Teddycloud. I finally succeeded but the process was a LOT of trial & error. Furthermore I had to search and read on dozens of dif…

Check if the container has access to the internet.

Check DNS resolve.

Here some commands I used:

/bin/sh => to open terminal

Curl -I https://www.srf.ch => Check if webpage can be ‘pinged’

cat /etc/resolv.conf => DNS entry

getent hosts google.com => DNS resolve