Just to update here also. There is a bug in the restore logic, if an app has a port configured, which does not exist in an old app package. If anyone here hits this also, please send an email to support and we can fixup you Cloudron for the moment. @rompo to come back to the initial issue during the update. Are you able to clone the app on your Cloudron and perform the update on the cloned instance? Just so we can see if this can be reproduced so we can debug that.

The package requires Cloudron 9 . @rompo if you can drop us your domain name at support@cloudron.io , I can enable the Cloudron 9 update.

Thanks for link to your changes. I've released a new package with those now.

Great that you managed to get this resolved quickly and thanks for sharing the solution.

I changed the accuracy and it got better. There is still a major delay of couple of minutes from "location data is received by traccar server" to "showing it on the traccar map"

@james the developer has released v5.1.1 which is supposed to have fixed the issue, however I am still experiencing the same behavior when I try to sign into the iOS app using OpenID. Can you please test on your iPhone and advise if it is the same for you as well?

@girish So after running a few tests it seems that Traccar does not like the domain to have a "/" at the end, no error logs to support this, but it does track with what was happening - typically my SSO system will want this, so I have made some changes, and it is all working now.

@axel0681 added!

@nebulon Thanks!

@girish Ah right, you have to tell it that user permissions have a number of devices... I thought it worked differently. Cheers, Aart

I've added the port now. It should be available to be enabled after you updated the app.

@nebulon Thanks works like a charm

The latest update has solved my problems and everything works fine.

@luckow my Traccar battery usage is only at 18% but that's still more than other apps. [image: 1655148081468-6bd62c16-f067-40a9-bfe3-48e770b7a242-image-resized.png] Will try to do a proper test tomorrow.

@girish Thank You! Absolutely no problem it's still "beta"