I noticed the option to use encryption on the iOS/Android clients and figured I would use the apache config i use for the web interface just on a different port pointed to the 5055 port.
ProxyPass / http://localhost:5055/
ProxyPassReverse / http://localhost:5055/
And it worked with my test client... But when I started moving multi-clients over I would get odd updates for different device id's. So client one would send data but the server thought it was client 2 and some times the opposite would happen. and with a third client in the mix it was even odder... Is there a config difference for the 5055 port proxy vs the web proxy needed.... I was running 3.9 and just upgraded to 3.10 so if it was fixed in that version I havent tested it yet...
Try to set "decoder.ignoreSessionCache" parameter to "true" in the config file.
That seems to work.. had 5-6 clients for the past few hours and none of odd issue... What's the penalty if there is one setting that parameter when we start loading 40-60 clients for some of our events?
I don't think there would be much performance impact. Traccar used to work like that by default and I have never heard of any issues.
I noticed the option to use encryption on the iOS/Android clients and figured I would use the apache config i use for the web interface just on a different port pointed to the 5055 port.
And it worked with my test client... But when I started moving multi-clients over I would get odd updates for different device id's. So client one would send data but the server thought it was client 2 and some times the opposite would happen. and with a third client in the mix it was even odder... Is there a config difference for the 5055 port proxy vs the web proxy needed.... I was running 3.9 and just upgraded to 3.10 so if it was fixed in that version I havent tested it yet...