Closed techtimo closed 2 years ago
Judging by the log you show, the Recorder is attempting to connect to MQTT on mqtt.no-cloud.eu:8883
which I don't think is actually what you're trying to accomplish.
For your own MQTT broker the password is indeed created with the mosquitto_passwd
program, so that is fine. On the Recorder side, the user and password are specified in the OTR_USER
and OTR_PASS
environment variables (or in config file, etc.), and this combination (given in clear text) must match the combination you specified when creating the Mosquitto password file entry.
Hi Jan Piet,
thanks for your prompt help! The I somewhat suppose that the port is also in the readme of the docker image.
Now the recorder is connected to the MQTT Server and I can see that the DB is still empty yet.
Best Greetings from Germany, Timo
Hi all, I need some support becasue I'm not able to get further for a few days here. I have a docker compose file running the MQTT broker and the owntracks recorder similar to the solution described here: https://github.com/owntracks/docker-recorder#all-in-one-solution-with-reverse-proxy-and-lets-encrypt
I have created the passwd file with the following command:
sudo docker run -it -v ..../mosquitto/conf/:/opt/mosquitto/config eclipse-mosquitto mosquitto_passwd -c /opt/mosquitto/config/passwd user
Looking at the file content it looks like it has been created properly. but the otrecroder container complains aboutIf I start the docker compose I get the following logs:
I can see that the passwd file is changed depending on the password I provide in the stdin. Then I update the env variables for the otrecorder:
But I continue to get the same issue.
I cannot find anything about how the password should be created for the broker in the booklet nor on github - I hope you can shed some light into my issue. Thanks
PS I think for OTR_CAFILE it should be enough to specify the bundle file from let's encrypt instead of creating this file with the 6 intermediate certs.