I’ve now got teddyclud running and at first glance everything looks good. Unfortunately I then found the following messages in the log.
Is that a problem?
ERROR|tls_adapter.c:0189:read_certificate| Failed to open ‘/teddycloud/certs/client/dcda0c002b68/ca.der’ for cert type detection
ERROR|tls_adapter.c:0376:load_cert| Loading cert ‘/teddycloud/certs/client/dcda0c002b68/ca.der’ failed
ERROR|tls_adapter.c:0189:read_certificate| Failed to open ‘/teddycloud/certs/client/dcda0c002b68/client.der’ for cert type detection
ERROR|tls_adapter.c:0376:load_cert| Loading cert ‘/teddycloud/certs/client/dcda0c002b68/client.der’ failed
ERROR|tls_adapter.c:0189:read_certificate| Failed to open ‘/teddycloud/certs/client/dcda0c002b68/private.der’ for cert type detection
ERROR|tls_adapter.c:0376:load_cert| Loading cert ‘/teddycloud/certs/client/dcda0c002b68/private.der’ failed
@t-power Check if you also see these lines in the logs:
INFO |tls_adapter.c:0197:read_certificate| File '/teddycloud/certs/client/ca.der' detected as DER style CERTIFICATE
INFO |tls_adapter.c:0197:read_certificate| File '/teddycloud/certs/client/client.der' detected as DER style CERTIFICATE
INFO |tls_adapter.c:0201:read_certificate| File '/teddycloud/certs/client/private.der' detected as DER style RSA PRIVATE KEY
As was explained to me by @0xbadbee teddycloud will use the certificates under /teddycloud/certs/client/ as a fallback so everything should be working.
If you want to resolve the issue you can create the directory dcda0c002b68 yourself.
For example (choose any other way you see fit) either find the host path for the docker volume and copy the certificates yourself also in /teddycloud/certs/client/dcda0c002b68/ or connect to the container and do it within the container.