Hello again.
I've made server update several times and always the same, never an issue.
Now, this last time (going from 6.12.2 to 6.14.5) most of the devices won't connect.
Only 1 gps model connects, others stay disconnected.
I found this in log file, maybe tells something:
2026-07-19 03:11:22 WARN: [Tbee5d6c6] error - Connection reset - SocketException (...)
2026-07-19 03:11:22 INFO: [Tbee5b6c6] disconnected
This repeats several times in between the messages from the connected devices, but I can't tell to which of the disconnected ones each message belongs.
Other than that, there's nothing out of the ordinary.
¿Perhaps some change in identifiers handling?
Because all non connected devices share the same issue with ID, I had to add a 0 before the actual device ID for them to connect.
¿Was that corrected?
Thank you for your time.
UPDATE:
The ones not working are "huabao" (JT808) protocol devices and only those.
Maybe protocol naming was changed?
I enable protocols using traccar.xml and if that changed, maybe I have to replace the current name for the new one.
¿where can I check for that? I found nothing on changelog.
UPDATE2:
Indeed, protocol naming changed. Replaced huabao by jt808 on traccar.xml and all started speaking with my server.
Thanks for your time, sorry for the inconvenience.
Problem solved.
Hello again.
I've made server update several times and always the same, never an issue.
Now, this last time (going from 6.12.2 to 6.14.5) most of the devices won't connect.
Only 1 gps model connects, others stay disconnected.
I found this in log file, maybe tells something:
This repeats several times in between the messages from the connected devices, but I can't tell to which of the disconnected ones each message belongs.
Other than that, there's nothing out of the ordinary.
¿Perhaps some change in identifiers handling?
Because all non connected devices share the same issue with ID, I had to add a 0 before the actual device ID for them to connect.
¿Was that corrected?
Thank you for your time.