Hi mein Problem ist, dass sich die Teddycloud sich nicht mit der Boxine Cloud verbindet und ich einen Zertifikat error habe:
Box CC3200 wird von der Teddycloud erkannt
danke
please use English.
the error is not relevant. but you could copy the 3 cert files from certs/client inte the to be created folder 38… and then the errors are gone.
The connection issue to boxine is another problem. do you use a local dns server and redirect all requests to prod.de.tbs.toys to teddycloud? if so, thats the problem.
there is a local dns server, a pihole. but there is all access. to prod.de.tbs.toys its on the whitelist.
teddycloud is running in docker with macvlan
thats my stack
Summary
services:
teddycloud:
container_name: teddycloud
hostname: teddycloud
image: Package teddycloud · GitHub
networks:
default:
ipv4_address: 192.168.1.90
#ports:
#- 80:80 #optional (for the webinterface)
#- 8443:8443 #optional (for the webinterface)
#- 443:443 #Port is needed for the connection for the box, must not be changed!
volumes:
- /volume1/docker/teddycloud/certs:/teddycloud/certs #certificates of the server
- /volume1/docker/teddycloud/config:/teddycloud/config config file for the server and the boxes
- /volume1/docker/teddycloud/content:/teddycloud/data/content #microSD representation for the boxes
- /volume1/docker/teddycloud/library:/teddycloud/data/library #library to manage content
- /volume1/docker/teddycloud/custom_img:/teddycloud/data/www/custom_img #location to store custom images for custom tonies json
- /volume1/docker/teddycloud/firmware:/teddycloud/data/firmware #firmware backups
- /volume1/docker/teddycloud/cache:/teddycloud/data/cache #img cache for content images
restart: unless-stopped
volumes:
certs:
config:
content:
library:
custom_img:
firmware:
cache:
networks:
default:
name: mvl
external: true
you might add an dns server esplicitly in your docker compose. it seems like tc could not resolve the url
In your teddycloud container
No, the host does not give an answer with its IPs behind it. In principle, ping is no guarantee that a name resolution will work.
there is an error in the console . ping: command not found
That won’t work out of the container either. What does it say in your resolv.conf?
docker exec -it yourcontainername cat /etc/resolv.conf
i think thats the problem
how can i fix it?
nano is not installed?