Anyone having issues with Umami since a few version ?

[benborges]

Hello cloudroners,

I have been quite busy but noticed already a few versions back that, Umami is not tracking anything, I was using the tracking code on 4 different static sites related to osintukraine project and all I know now is that, the tracking is not functioning properly, previously the expected behavior was that by visiting the target site, the realtime dashboard was showing in real time visitors and some analytics, now no matter what I try, I can't have anything showing up.

I even tested on my own blog and it's the same, it's like no data is being captured/sent
I have looked at the logs but I can't find any hint to look for to start debugging this.

Can anyone replicate this issue on their side ?

[jdaviescoates]

Yes, updating to version 2 was a major update and it seems things are broken since then. I've not tried it yet, but I'm assuming that if I just create new tracking codes it'll start working again...

[benborges]

@jdaviescoates I'm trying it now, just installed it yesterday for my own blog and I'm getting nothing, this is a clean fresh install

[robi]

Could this be a CORS issue?

[girish]

@benborges Strange, let me test...

[d19dotca]

Doesn't happen to be related at all to https://forum.cloudron.io/topic/9145/umami-2-2-0-tracker-xhr-request-works-only-on-every-second-app-restart/19 does it, @benborges? If you restart the app and visit one of the tracked sites, does the Umami dashboard then show new data?

[benborges]

@d19dotca Interesting, on the new fresh install, I restarted and voila, it works !

on my old install, the one I don't want to loose the site ID's (even if I lost the historical data, that's fine)

I see this error after restart :

 ==> Starting Umami
May 26 10:33:14
May 26 10:33:14
May 26 10:33:14 Inconsistent column data: Error creating UUID, invalid character: expected an optional prefix of `urn:uuid:` followed by [0-9a-zA-Z], found `u` at 1
May 26 10:33:14 Invalid `prisma.website.findUnique()` invocation:
May 26 10:33:14 PrismaClientKnownRequestError:
May 26 10:33:14 at async NextNodeServer.runApi (/app/code/node_modules/next/dist/server/next-server.js:514:9)
May 26 10:33:14 at async NextNodeServer.runImpl (/app/code/node_modules/next/dist/server/base-server.js:432:29) {
May 26 10:33:14 at async Object.apiResolver (/app/code/node_modules/next/dist/server/api-utils/node.js:372:9)
May 26 10:33:14 at async Object.fn (/app/code/node_modules/next/dist/server/next-server.js:828:35)
May 26 10:33:14 at async Router.execute (/app/code/node_modules/next/dist/server/router.js:243:32)
May 26 10:33:14 at async __WEBPACK_DEFAULT_EXPORT__ (/app/code/.next/server/pages/api/websites/[id].js:154:25)
May 26 10:33:14 at async t._request (/app/code/node_modules/@prisma/client/runtime/library.js:179:10484)
May 26 10:33:14 at pn.handleAndLogRequestError (/app/code/node_modules/@prisma/client/runtime/library.js:176:5907)
May 26 10:33:14 at pn.handleRequestError (/app/code/node_modules/@prisma/client/runtime/library.js:176:6477)
May 26 10:33:14 at pn.request (/app/code/node_modules/@prisma/client/runtime/library.js:176:5786)
May 26 10:33:14 clientVersion: '4.13.0',
May 26 10:33:14 code: 'P2023',
May 26 10:33:14 message: 'Error creating UUID, invalid character: expected an optional prefix of `urn:uuid:` followed by [0-9a-zA-Z], found `u` at 1'
May 26 10:33:14 meta: {
May 26 10:33:14 }