Anybody got MQTT/SSL working with Teltonika routers?
I’m trying to setup one-way SSL connection towards a Thingsboard server on an EOL Teltonika TRB245.
The TRB triggers the Java bug:
“Insufficient buffer remaining for AEAD cipher fragment”
If I use the same certificate on a Linux/mosquitto_pub it works, but the TRB triggers the fault.
Is there a workaround? A newer model that works?
Greetings,
Whenever possible, could you please try to change the TLS version being used by both, the Thingsboard platform & the TRB gateway to either 1.1 or 1.3? I believe thingsboard uses 1.2 by default and I would like to eliminate the version fault as a potential cause for your issue.
Additionally, you can look into this Wiki example, you may have missed some settings potentially, so it would be good to double-check: Monitoring with ThingsBoard IoT Platform - Teltonika Networks Wiki
Regards,
M.
Thanks for replying!
I got it working from TRB with unsecure MQTT. All I do is change port, setting secure, and adding my certificate authority file, this triggers the Java fault in Thingsboard.
And as I said, using the exact same certificate I can get it working with a mosquitto client from an other Linux machine to the same Thingsboard device.
I tried to force Thingsboard into TLSv1.3, but no change.
From snooping packets on my Thingsboard server it looks like the TRB is using TLSv1.3 default.
How do I force the TRB to use TLSv1.2? Can not find this from the WebUI?
I am on latest fw: TRB2_R_00.07.14.4
Hello,
First, I’m glad that you seem to have resolved the issue.
As for changing the TLS version, you can find it under the Broker settings:
Regards,
M.
Thanks!
I’m just trying to use the built in MQTT client from “Data to Server”, didn’t have the MQTT package installed. I guess I can’t change it from there only?
So I need a MQTT broker in between in some way? I have to look at this.
I just want to achive this (Thingsboard call it one-way SSL):
mosquitto_pub --cafile ca-root.pem -d -q 1 -h "YOUR_TB_HOST" -p "8883" \
-t "v1/devices/me/telemetry" -u "YOUR_ACCESS_TOKEN" -m {"temperature":25}
Hello,
Apologies if I misunderstood - to begin with, I believe you mentioned that the issue has been resolved with the use of an insecure MQTT connection, is that correct?
Secondly, could you clarify what data you’re reading/sending to Thingsboard exactly? From the command you’ve provided in your latest reply, I understand that our device is a publisher, while Thingsboard is the broker. Could you confirm that just so I’m sure? Lastly, if you could, kindly clarify whether the provided Wiki example with the Thingsboard configuration has helped you in any way or not.
Regards,
M.
Yes, unsecure MQTT works from the “Data to Server” setup.
Final goal is to use modbus data from RS485 setup “Modbus Serial Client” + other internal TRB data available there (like mobile data usage etc.) and send it to TB.
Yes, TRB as publisher and TB as broker/receiver and, yes, pretty much as the Wiki example!
Problem arise when I apply the secure verion of MQTT, then TB triggers the Java error and no data gets through.
I will try to setup with the TRB broker from the MQQT package in between
Hello,
Thank you very much for the clarification, update us on how it goes.
Regards,
M.
Yes, got it working with the MQTT broker in the middle.
Changed my “Data to Server” setup do MQTT pointing to localhost:1883
Activated broker on 1883, setup a relay using SSL/port 8883 towards Thingsboard.
No error,
it was working with both TLSv1.2 and TLSv1.3.
So, fine, there must be something different in the MQTT publisher you use within “Data to
Server”, and the broker you use from the MQTT package?
This topic was automatically closed after 60 days. New replies are no longer allowed.