Updates from Traccar Android Client sporadically stop getting parsed?

Hey there,

since a few days, I encounter the issue, that for one device, an android traccar client, the locations do not get parsed, as far as I interpret the logs, anymore. It is strange as it is only this one client but it is not the only android client - the others are working, however, they have another version. If I restart the traccar server, location updates get digested again without touching the client. After a while, it stops working again.

The server is running on docker behind a nginx reverse proxy and with OpenID.

Server version: 6.3, latest docker tag
Client version: Build/AP2A.240805.005.A1
Server log where no locations are parsed:

2024-08-10 09:45:35  INFO: [T01f0d6a7] connected
2024-08-10 09:45:35  INFO: [T01f0d6a7: osmand < 127.0.0.1] POST /?id=xx×tamp=1723273733&lat=xx&lon=yy&speed=3.518357528772354&bearing=32.70000076293945&altitude=842.0&accuracy=0.0&batt=92.0&charge=true HTTP/1.1\r\nUser-Agent: Dalvik/2.1.0 (Linux; U; Android 14; Pixel 8a Build/AP2A.240805.005.A1)\r\nX-Forwarded-For: 10.2.180.3\r\nAccept-Encoding: gzip\r\nX-Real-IP: 10.2.180.3\r\nX-Forwarded-Server: xyz\r\nContent-Type: application/x-www-form-urlencoded\r\nVia: 1.1 747e06cb3bba\r\nX-Forwarded-For: 172.26.0.3\r\nX-Forwarded-Proto: http\r\nX-Forwarded-Host: xyz\r\nX-Forwarded-Server: 172.26.0.2\r\nHost: localhost:5055\r\nContent-Length: 0\r\n\r\n
2024-08-10 09:46:05  INFO: [T01f0d6a7] disconnected
2024-08-10 09:46:21  INFO: [T4632be2e] connected
2024-08-10 09:46:21  INFO: [T4632be2e: osmand < 127.0.0.1] POST /?id=xx×tamp=1723273733&lat=xx&lon=yy&speed=3.518357528772354&bearing=32.70000076293945&altitude=842.0&accuracy=0.0&batt=92.0&charge=true HTTP/1.1\r\nUser-Agent: Dalvik/2.1.0 (Linux; U; Android 14; Pixel 8a Build/AP2A.240805.005.A1)\r\nX-Forwarded-For: 10.2.180.3\r\nAccept-Encoding: gzip\r\nX-Real-IP: 10.2.180.3\r\nX-Forwarded-Server: xyz\r\nContent-Type: application/x-www-form-urlencoded\r\nVia: 1.1 747e06cb3bba\r\nX-Forwarded-For: 172.26.0.3\r\nX-Forwarded-Proto: http\r\nX-Forwarded-Host: xyz\r\nX-Forwarded-Server: 172.26.0.2\r\nHost: localhost:5055\r\nContent-Length: 0\r\n\r\n
2024-08-10 09:46:51  INFO: [T4632be2e] disconnected

Server log where locations of the same client are parsed after server restart:

2024-08-10 17:02:38  INFO: [T97caa1ae] connected
2024-08-10 17:02:38  INFO: [T97caa1ae: osmand < 127.0.0.1] POST /?id=00×tamp=1723302158&lat=xx&lon=yy&speed=4.295895314151764&bearing=80.30000305175781&altitude=810.0&accuracy=0.0&batt=68.0 HTTP/1.1\r\nUser-Agent: Dalvik/2.1.0 (Linux; U; Android 14; Pixel 8a Build/AP2A.240805.005.A1)\r\nX-Forwarded-For: yy\r\nAccept-Encoding: gzip\r\nX-Real-IP: yy\r\nX-Forwarded-Server: xxx\r\nContent-Type: application/x-www-form-urlencoded\r\nVia: 1.1 5debcf8fbff7\r\nX-Forwarded-For: 172.26.0.3\r\nX-Forwarded-Proto: http\r\nX-Forwarded-Host: xxx\r\nX-Forwarded-Server: 172.26.0.2\r\nHost: localhost:5055\r\nContent-Length: 0\r\n\r\n
2024-08-10 17:02:38  INFO: Event id: 00, time: 2024-08-10 17:02:38, type: deviceMoving, notifications: 0
2024-08-10 17:02:38  INFO: [T97caa1ae] id: 00, time: 2024-08-10 17:02:38, lat: xx, lon: yy, speed: 4.3, course: 80.3
2024-08-10 17:02:38  INFO: [T97caa1ae: osmand > 127.0.0.1] HTTP/1.1 200 OK\r\ncontent-length: 0\r\n\r\n
Anton Tananaev3 months ago

You have to upgrade to 6.4.

okay, thanks! To easy to get to this idea...

6.4. is not available yet on docker hub. Have to wait. but thanks a lot!