-
-
Notifications
You must be signed in to change notification settings - Fork 285
Closed
Labels
Description
Is this a bug or a feature request?
Somewhere between a bug, a feature, and some info on the docs I guess ;)
What did you expect?
Well, I don´t know what file format to use for the --mqtt-ca-cert option
What happened?
I used pem and der format for the CA, but I got this error:
ERRO[0000] could not setup mqtt backend, retry in 2 seconds: Network Error : x509: certificate signed by unknown authorityAlso, just to try, I passed any other file (not a certificate, i.e. the start.sh file suggested for kelink), and it gives the same error, it doesn't tell me there's an error on the certificate itself.
What version are your using?
lora-gateway-bridge version 2.1.5How can your issue be reproduced?
Just try to use the --mqtt-ca-cert option not knowing the right certificate format ;)
/user/lora-gateway-bridge/bin/lora-gateway-bridge --mqtt-server ssl://dev-marting-3.exo.local:1883 --mqtt-ca-cert /user/lora-gateway-bridge/certnew.cerCould you share your log output?
/user/lora-gateway-bridge/bin/lora-gateway-bridge --mqtt-server ssl://dev-marting-3.exo.local:1883 --mqtt-ca-cert /user/lora-gateway-bridge/certnew.cer
INFO[0000] starting LoRa Gateway Bridge docs="https://docs.loraserver.io/lora-gateway-bridge/" version=2.1.5
INFO[0000] backend: connecting to mqtt broker server="ssl://dev-marting-3.exo.local:1883"
ERRO[0000] could not setup mqtt backend, retry in 2 seconds: Network Error : x509: certificate signed by unknown authority
INFO[0002] backend: connecting to mqtt broker server="ssl://dev-marting-3.exo.local:1883"
ERRO[0002] could not setup mqtt backend, retry in 2 seconds: Network Error : x509: certificate signed by unknown authority