Hi there, 
So this is probably my last attempt to get help or information in the openBalena Forums. 
I always get this error, the deployment is based on a KVM-VM with a public Ip address and DNS entries set for :
- api.ob-test.redacted-domainname.de
- registry.ob-test.redacted-domainname.de
- vpn.ob-test.redacted-domainname.de
- s3.ob-test.redacted-domainname.de
- tunnel.ob-test.redacted-domainname.de
all pointing to its public IP-Address of my Server/VM
The Docker Compose Up runs smoothly, with no errors or warnings that aren’t expected so far.
Is there a fix for this misbehavior? Because obviously, that .crt file is not in place, and I would figure that it is most likely the acme that is failing, if I wouldn’t get an “OK” on the API endpoint:
I already asked a question related to the balena-CLI which ultimately leads to this error because there is obviously a self-signed certificate installed, even though I used the “-c” for acme in the installation process:
./scripts/quickstart -c -p -d ob-test.redacted-domainname.de -U ******** -P **********
Here is a link to my other Thread about the CLI problem: (it is still unanswered anyways)
Please don’t get me wrong or anything, I like the idea of how balena wants to solve IOT related situations, we in general here at our company really would love to test compatibility to maybe even switch completely with 300+ Devices to balenaCloud, but as long as I can tell, support is most likely the only way to get help from balena. This is not what I was expecting, especially because other threads, with sometimes really easy beginner issues get an answer and help. Whereas myself was greatly ignored for issued by now.
Have a good one, I would love to hear at least a “hi” or “we don’t have a clue either” or “please give more information”
