Hi,
First off, great platform.. I'm just moving from Owntracks as this seems far more reliable. I have two bugs:
It seems that when using IIS URL Rewrite to enable SSL that the server ignores device ID. I have two devices connected (iphone and android) and they both have different IP's. When I connect on the local network they work fine, but when I connect remotely over the mobile network (at this point the traffic goes over SSL) that the server doesn't parse the unique ID. I wonder if if its using the source IP as the key for the device (as they have unique IP's on the local network) but on the mobile network all the traffic to 5055 effectively comes from 127.0.0.1 for all devices.
I'm consistently getting errors in the log related to parsing the data:
2016-10-14 00:03:58 DEBUG: [1010EDE7: 5055 > 127.0.0.1] HEX: 485454502f312e3120323030204f4b0d0a436f6e74656e742d4c656e6774683a20300d0a0d0a
2016-10-14 00:03:58 WARN: [1010EDE7] error - NullPointerException (WebDataHandler:98 < *:140 < BaseDataHandler:29 < ... < ExtendedObjectDecoder:61 < ...)
2016-10-14 00:03:58 INFO: [1010EDE7] disconnected
2016-10-14 00:04:28 INFO: [2B40F197] connected
2016-10-14 00:04:28 DEBUG: [2B40F197: 5055 < 127.0.0.1] HEX: 474554202f3f69643d3131312674696d657374616d703d31343736333939383637266c61743d35312e393030393435266c6f6e3d2d322e3132373430302673706565643d302662656172696e673d3026616c746974[truncated for readability]74656e74496e666f726d6174696f6e3d312e302c204d6178436f6e74656e74496e666f726d6174696f6e3d322e300d0a0d0a
2016-10-14 00:04:28 DEBUG: [2B40F197: 5055 > 127.0.0.1] HEX: 485454502f312e3120323030204f4b0d0a436f6e74656e742d4c656e6774683a20300d0a0d0a
2016-10-14 00:04:28 WARN: [2B40F197] error - NullPointerException (WebDataHandler:98 < *:140 < BaseDataHandler:29 < ... < ExtendedObjectDecoder:61 < ...)
2016-10-14 00:04:28 INFO: [2B40F197] disconnected
2016-10-14 00:04:59 INFO: [EFB08B7F] connected
2016-10-14 00:04:59 DEBUG: [EFB08B7F: 5055 < 127.0.0.1] HEX: 474554202f3f69643d3131312674696d657374616.[I've truncated]50d0a582d5032502d50656572446973743a2056657273696f6e3d312e310d0a582d5032502d506565724469737445783a204d696e436f6e74656e74496e666f726d6174696f6e3d312e302c204d6178436f6e74656e74496e666f726d6174696f6e3d322e300d0a0d0a
2016-10-14 00:04:59 DEBUG: [EFB08B7F: 5055 > 127.0.0.1] HEX: 485454502f312e3120323030204f4b0d0a436f6e74656e742d4c656e6774683a20300d0a0d0a
2016-10-14 00:04:59 WARN: [EFB08B7F] error - NullPointerException (WebDataHandler:98 < *:140 < BaseDataHandler:29 < ... < ExtendedObjectDecoder:61 < ...)
2016-10-14 00:04:59 INFO: [EFB08B7F] disconnected
Here's the IIS Log:
2016-10-14 11:26:24 192.168.0.5 GET / id=444×tamp=1476444384&lat=XX.900910&lon=XX.127312&speed=0&bearing=264.375&altitude=44.7649&batt=0&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=791eb692-3204-49d7-8642-a2929cb376c7&SERVER-STATUS=200 4443 - XX.69.144.114 TraccarClient/3.1+CFNetwork/808.1.4+Darwin/16.1.0 - 200 0 0 49
2016-10-14 11:26:27 192.168.0.5 GET / id=444×tamp=1476444387&lat=XX.900910&lon=XX.127312&speed=0&bearing=264.375&altitude=44.7219&batt=0&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=c79127ec-b2bd-4c76-8c61-db74defad6f9&SERVER-STATUS=200 4443 - XXX.69.144.114 TraccarClient/3.1+CFNetwork/808.1.4+Darwin/16.1.0 - 200 0 0 53
2016-10-14 11:26:31 192.168.0.5 GET / id=444×tamp=1476444391&lat=XX.900910&lon=XX.127312&speed=0&bearing=264.375&altitude=44.6644&batt=0&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=fbb30e09-96e0-4a08-a5cd-57e3af912202&SERVER-STATUS=200 4443 - XX.69.144.114 TraccarClient/3.1+CFNetwork/808.1.4+Darwin/16.1.0 - 200 0 0 51
2016-10-14 11:26:35 192.168.0.5 GET / id=444×tamp=1476444395&lat=XX.900910&lon=XX.127312&speed=0&bearing=264.375&altitude=44.6043&batt=0&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=9840caf9-68bd-41e4-b44e-328e645447cb&SERVER-STATUS=200 4443 - XX.69.144.114 TraccarClient/3.1+CFNetwork/808.1.4+Darwin/16.1.0 - 200 0 0 52
2016-10-14 11:26:39 192.168.0.5 GET / id=444×tamp=1476444399&lat=XX.900910&lon=XX.127312&speed=0&bearing=264.375&altitude=44.6468&batt=0&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=350e7b22-b0ec-4c5d-8e23-0629a8bd64fa&SERVER-STATUS=200 4443 - XX.69.144.114 TraccarClient/3.1+CFNetwork/808.1.4+Darwin/16.1.0 - 200 0 0 50
2016-10-14 11:26:41 192.168.0.5 GET / id=222×tamp=1476444400&lat=XX.90095044327548&lon=XX.1269686988894496&speed=1.7269819526317118&bearing=337.10546875&altitude=132.8841321400846&batt=87.0&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=9f3d8959-8343-41f7-a59a-5e0ff5311e90&SERVER-STATUS=200 4443 - 82.33.187.230 Dalvik/2.1.0+(Linux;+U;+Android+5.1.1;+SM-G800F+Build/LMY47X) - 200 0 0 47
2016-10-14 11:26:42 192.168.0.5 GET / id=444×tamp=1476444402&lat=XX.900910&lon=XX.127312&speed=0&bearing=264.375&altitude=44.7308&batt=0&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=07a64efa-ccd3-4390-8a5d-6fd1ba81f0d5&SERVER-STATUS=200 4443 - XX.69.144.114 TraccarClient/3.1+CFNetwork/808.1.4+Darwin/16.1.0 - 200 0 0 50
2016-10-14 11:26:46 192.168.0.5 GET / id=444×tamp=1476444406&lat=XX.900910&lon=XX.127312&speed=0&bearing=264.375&altitude=44.6193&batt=0&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=849adc83-22e3-4fa0-91af-f6822285f8c5&SERVER-STATUS=200 4443 - XX.69.144.114 TraccarClient/3.1+CFNetwork/808.1.4+Darwin/16.1.0 - 200 0 0 58
2016-10-14 11:26:50 192.168.0.5 GET / id=444×tamp=1476444410&lat=XX.900910&lon=XX.127312&speed=0&bearing=264.375&altitude=44.6382&batt=0&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=ab481002-c5b4-40b3-9af6-b8c772c84de5&SERVER-STATUS=200 4443 - XX.69.144.114 TraccarClient/3.1+CFNetwork/808.1.4+Darwin/16.1.0 - 200 0 0 51
2016-10-14 11:26:54 192.168.0.5 GET / id=444×tamp=1476444414&lat=XX.900910&lon=XX.127312&speed=0&bearing=264.375&altitude=44.6432&batt=0&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=7d420f3b-a166-4b4a-a730-4a4ec74f2390&SERVER-STATUS=200 4443 - XX.69.144.114 TraccarClient/3.1+CFNetwork/808.1.4+Darwin/16.1.0 - 200 0 0 52
2016-10-14 11:26:57 192.168.0.5 GET / id=444×tamp=1476444417&lat=XX.900910&lon=XX.127312&speed=0&bearing=264.375&altitude=44.6606&batt=0&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=b740521f-5021-4e22-af38-33c0605ccd02&SERVER-STATUS=200 4443 - XX.69.144.114 TraccarClient/3.1+CFNetwork/808.1.4+Darwin/16.1.0 - 200 0 0 50
2016-10-14 11:27:01 192.168.0.5 GET / id=444×tamp=1476444421&lat=XX.900910&lon=XX.127312&speed=0&bearing=264.375&altitude=44.5894&batt=0&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=1146fa9c-2c3a-4982-9303-75fbc69d02fb&SERVER-STATUS=200 4443 - XX.69.144.114 TraccarClient/3.1+CFNetwork/808.1.4+Darwin/16.1.0 - 200 0 0 61
2016-10-14 11:27:04 192.168.0.5 GET / id=444×tamp=1476444424&lat=XX.900910&lon=XX.127312&speed=0&bearing=264.375&altitude=44.6524&batt=0&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=238e5c9c-9a3d-4867-b6a6-4baa2b66750c&SERVER-STATUS=200 4443 - XX.69.144.114 TraccarClient/3.1+CFNetwork/808.1.4+Darwin/16.1.0 - 200 0 0 52
2016-10-14 11:27:07 192.168.0.5 GET / id=444×tamp=1476444427&lat=XX.900910&lon=XX.127312&speed=0&bearing=264.375&altitude=44.6937&batt=0&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=da59feee-ef18-4cf4-a527-a2ff06ec883e&SERVER-STATUS=200 4443 - XX.69.144.114 TraccarClient/3.1+CFNetwork/808.1.4+Darwin/16.1.0 - 200 0 0 52
Any thoughts?
Walking the source it does look like you generate a 'session' ultimately tied to the source IP so any data received from that IP regardless of ID gets treated as that ID?
Is that the current behaviour?
Thanks!
When will the next release be? Just wondering if I need to make a build environment or wait for a binary build?
It's the standard setup with IIS terminating the SSL and rewriting the URL with the IP of the SSL terminator instead of the client. I think the SSL terminator is a red herring as I believe it does it without (I'll check). I'm all windows based.
Thank you for the help, it's appreciated.
Ian
Please double-check everything again. If it still doesn't work, I would need to look myself.
Hi,
First off, great platform.. I'm just moving from Owntracks as this seems far more reliable. I have two bugs:
It seems that when using IIS URL Rewrite to enable SSL that the server ignores device ID. I have two devices connected (iphone and android) and they both have different IP's. When I connect on the local network they work fine, but when I connect remotely over the mobile network (at this point the traffic goes over SSL) that the server doesn't parse the unique ID. I wonder if if its using the source IP as the key for the device (as they have unique IP's on the local network) but on the mobile network all the traffic to 5055 effectively comes from 127.0.0.1 for all devices.
I'm consistently getting errors in the log related to parsing the data:
Here's the IIS Log:
Any thoughts?