Umami 2.2.0 tracker XHR request works only on every second app restart

[stefano]

Fresh install. I installed Umami for the first time on May 13th.

The installed versions are:

App Title and Version: Umami 2.2.0
Package Version: is.umami.cloudronapp@3.1.0

[girish]

@stefano I missed your initial post about your setup. Do you see the same behavior with different browsers and ad block extensions disabled? I will try to reproduce this again in the meantime.

[stefano]

Ok, no worries

Yes, it doesn't depend on the browser. I tried with Chrome, Edge, Firefox and Brave (even with shields off), without any ad-blocking extension enabled.

[d19dotca]

@girish just wanted to ask about an update on this one.

[girish]

@d19dotca will try this again...

[girish]

Out of curiosity, is anyone else seeing this behavior?

[Meuschke]

@girish It seems that this behavior happens for me too.
This seems to be browser independent. Restarting the Umami application then helps.

[girish]

I tried to reproduce this but I am not able to. Here's what I did:

• Install umami
• Add domain in umami.
• Install surfer
• Put tracking code from umami into a sample index.html
• I refresh index.html 10 times. I see 10 in umami

Is there something special I need to do?

[stefano]

Try restarting either Umami or rebooting the server, after that Umami should stop working (you will see an error in the browser's console when loading the site).
Then after restarting/rebooting again, it will work again.

Basically it stops working every other reboot, so when a reboot is needed I need to reboot twice to get Umami to work.

Not sure if it matters, but in my case the website I am tracking is on a different server than Umami.

[girish]

@stefano thanks! I can reproduce it.

[girish]

Alright, https://github.com/umami-software/umami/issues/2093 . The issue is that the geolocation db is being removed when we build the app on restart. I tried to debug a lot but couldn't figure out.

[d19dotca]

Thanks for looking into this! I’m glad it’s not just me and others have seen this too. I know you said you couldn’t reproduce it a while back so assumed maybe it was an issue on my end, glad to know it’s something more with Umami and the build part. Thanks for sticking with it, @girish. And thanks to everyone else here commenting with their “me too” as well.

[robi]

@girish would it help to move the location of the geo db?

[girish]

@robi the location is hardcoded in the code. I still don't understand why or who remove the geo database. It is just building the app....

[robi]

@girish perhaps an inadvertent cleanup of *

[girish]

@d19dotca @Meuschke this should be finally fixed in the latest update.