that works as expected. Ok. Next two steps. Edit you container. Switch to Manage Variables. Create new variable. Choose Matomo Configuration. Go down to Tracking Request Target Path and switch from piwik.php to js/

The idea behind containers: Insert the matomo Tag Manager code into your website only once. If you work with a matamo expert, they can configure matomo without having to change the code on the live website. The container changes every time you change the configuration.

You can change the endpoint in the variables. The moment we switch from piwik.php to js/ your website sends data to matomo.example.com/js/ instead of matomo.example.com/piwik.php

If you use the file manager from App settings and open js/index.php you see

require_once DIR . '/tracker.php'

If you open tracker.php you find the require once which throws errors in the logfile.

require_once PIWIK_INCLUDE_PATH . '/libs/upgradephp/upgrade.php';

@girish I found this answer:

Tracking 1 million page views per month or less

One server can be sufficient to host both the database and app server
App server minimum recommended configuration: 4 CPU, 8 GB RAM, 250GB SSD disk.

@jfrere this got recently fixed - https://github.com/ip2location/ip2location-piwik/issues/91#event-11698953657

Also https://matomo.org/faq/troubleshooting/faq_25610/

@girish since I recently had another issue as well, I was just thinking that maybe all this is related to the fact that I initially migrated from an older Piwik installation.
With that, I mean that after I installed the Cloudron app about 2 years ago, I imported existing data from that older Piwik installation. This might explain why I'm faced with those issues during upgrades while others aren't 🤔

Great, thanks for sharing your solution!

@girish, fair enough.
I definitely understand your reasoning, but on the other side there is probably a good reason why the issue was added to the Matomo FAQ 🤔

This is a FABULOUS found, it makes every website/domain on Cloudron having it’s own analytics domain and it works flawless!!

@SamGreenwood on which page/section is this? All the pages of matomo?

@girish thanks!

Can you share what stats you use, and how similar or different they are from the stats NodeBB has by default?

@d19dotca said in Hosting this is insanely expensive:

Umami

Yeah, I've never really used any analytics that much, but I really like Umami because it just so simple and easy, does the basics really nicely, and displays the information clearly.

Seems the latest release fixed the issue, I presume because they modified the plugin code for the LDAP access to Matomo. 🙂 Can mark this as Solved I think.

@shrey this should be fixed now in the latest update.

@jdaviescoates Fixed, thanks. That text was originally copied from matomo itself. I think they are a french company and thus the typo (as in, I think measure is mesure in french, maybe....)

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 🙂