If it's password issue, there are some instructions here - https://matomo.org/faq/how-to/faq_191/

@nebulon That's fair. I guess I assumed they were sort of paired together as my understanding for disabling the auto-archiving in the web part was specifically for speed gains which you guys had already done by setting up crons instead for archiving reports, so the KB I linked to seemed relevant to that assumption that we wanted Matomo to be configured for speed instead of convenience. But I can appreciate that you want to keep the amount of customizations to be as slim as possible.

@micmc agreed, this should be a configurable message by the admin to get the wayward user back on track via home page, landing or support resources.

Hey @sydney,
I tried regexr.com. The regex seems to be correct. However, I still get the error message. No idea what is wrong here.
But thanks for your engagement 🙂

The MySQL+SSH tunnel info is here - https://forum.cloudron.io/topic/3237/remote-sql-support-on-a-per-app-basis . If you are feeling brave (I don't recommend this at all), there are some socat tricks I posted a while ago - https://forum.cloudron.io/topic/3237/remote-sql-support-on-a-per-app-basis

@girish Thanks, now I managed to migrate the existing installation with the latest Matomo app package.
It was really straightforward!

Ah interesting, I thought they were already in the main admin account given they said:

logged in my main cloudron user

haha. Oh well, good to know it's resolved now. 🙂

@nebulon thanks!!!!!

@girish Seems the latest app package update fixes it. Thanks for the quick turnaround as always! 🙂

For reference only (I accidentally duplicated this in a new post, didn't see this one until later): https://forum.cloudron.io/topic/4924/matomo-system-check-report-showing-a-warning-for-load-data-infile-with-access-denied-as-the-root-cause/

Edit: Latest app package update fixes the issue.

@girish
I want to install Performance Audit. This module is a Marketplace Module. If I click/install it, it will be put under /plugins.
If I move it to a newly created plugins.local, the system will not recognize it. not in the marketplace section, that it can be used or in the plugins section.
maybe there is a matomo/cloudron folder mapping issue?.
If I activate/install it via UI I still get the error I described…

@dgarsys Thank you, that resolved it

@cbeams Everything works as expected now against v1.24.0, thanks!

@cbeams OK, turns out it wasn't fixed - back to short logout times. Very strange, some software designers really don't seem to think this sort of thing is an issue, clearly over absorbed in their own ideas and under appreciative of users.

@d19dotca Yeah, I get what you're saying. The process is not that bad though. As long as you keep the same settings, it's a drop and drop of the files and hitting the start button. It'll save them to the folder you had specified on a previous run and you'll be doing two things as once, resizing and crunching (less work for the server).

@imc67 Good detective work!

So, we found that the issue is because the memory limit settings are currently not set for "app task" processes but only for backup tasks. Should have this fixed for the next release.

For what it's worth, if this helps at all, I have always logged in with the default admin account but then set my LDAP user as a super admin, then logged out and logged back in as the LDAP user and as a super admin I removed the default admin account. That way I effectively replace the default admin account with my own LDAP user.

Looks like the form expired somehow, strange. Will mark this as resolved in any case.

@d19dotca Yeah, I tried updating it yesterday but there is a file integrity warning (something to do with the less tool). Have to investigate and/or report upstream.

Okay so after multiple file integrity issues ("X does not exist"), I opted to install a new Matomo instance, and migrated the data from old to new. It seems to be working well and passes all system checks now. I think this can be marked resolved. I still don't know how it ever got into that state, but it's good again. 🙂

@marcusquinn Thanks Marcus!

@marcusquinn The funny thing about that is that I didn't believe the Firefox settings actually worked lol.. more like they wouldn't be honored, especially by closed source apps.

Edit: @marcusquinn In that case, I'll start using it instead of Decentraleyes.

@girish Thank you! 🙂 I updated and can confirm it's working as expected now with only the one LDAP server listed.

Somehow fixed by running the reset link in the plugin Settings > Support. No idea what setting was wrong but happy to confirm not a Cloudron issue. Sorry for the bother, was just eliminating possibilities.

Solved. Thanks 🙂

@girish A fresh install already has it set to "No"? Interesting, I don't recall ever setting mine to "Yes", but I guess I did. Thank you for confirming, seems it's okay then if it's set to "No" by default and the cronjob is doing it automatically.