We sill can’t make it work.
Using MQTT windows client with the exact same settings works. TLS1.2, MQTT 3.1, CA signed server certificate, 1.1.0060_Release r198 firmware.
I have to decide which gateways to buy and RAK was the best option…
Does anyone had the same issue?
PD: The broker is behind HAproxy (voyager ingress) using Let’sEncypt certificates
PD: Maybe I need OpenWRT ca-bundle package? can’t install it as it seems that opkg package manager doesnt have repositories configured
I’m still unable to make our RAK gateways work with our ChirpStack instance… is there someone with the same issue? or someone who can give me support?
Thanks in advance!
We’re using EMQX 3.2.3 which supports 3.1, 3.1.1 and 5.0: (from Github)
Starting from 3.0 release, EMQ X broker fully supports MQTT V5.0 protocol specifications and backward compatible with MQTT V3.1 and V3.1.1, as well as other communication protocols such as MQTT-SN, CoAP, LwM2M, WebSocket and STOMP.
Hi @yutao. My problem persists.
I’ve checked our Ingress setup and it works like expected. We’re using Voyager Ingress which uses HAProxy for load balancing.
ChirpStack Gateway Bridge and other clients like MQTT.fx can connect normally to our broker.
Hi there!
I upgraded our EMQX instance to 4.0.2, nicer dashboard but same results.
Also downgraded FW to 1.1.0059_Release r197 (also tried V1.1.0050_Release_r184) with no luck.
Still having ERR 14.
We could try to bypass Voyager ingress and load Let’sEncrypt certificates to EMQX broker but that will take time and downtime for our current services. Also 90day renewal brings a lot of work. This has become a very big issue for us, we need to deploy an indoor network in a new client in 1 week and we’ve decided to use RAK for all of our deployments.