What's your go to product for site stats?

[phenomlab]

@DownPW what’s the output of the url you are using for the script in the NodeBB headers if you try to access it directly?

[DownPW]

With no proxy I access to the js script :

But It seems that umami doesn’t like reverse proxy. I access to umami on https with nginxproxy without problem but I have this now when I try to access the web site configuration (Edit) :

[phenomlab]

@DownPW said in What's your go to product for site stats?:

But It seems that umami doesn’t like reverse proxy

It does because that’s how I run it

[phenomlab]

@DownPW Just tested the reverse proxy and it appears fine.

[DownPW]

On your configuration I guess not mine.
My reverse proxy working for me too but the bug appear when I click here :

I give you my password in PM

[phenomlab]

@DownPW As discussed in PM, it appears that this section was actaully missing

Have run this on your instance, and all working

[Sala]

Gdpr has been hitting my blog, with the majority of web traffic coming from the EU. I learn that Gdpr has the power to turn your page into a visitor in an error form like 403, 503 type. I was wondering, but after a long chat with Yandex, I realized it was Gdpr that we need to change how we operate in collecting data.

[phenomlab]

@Sala If you are receiving visitors from the EU then you need to comply with the GDPR. If you haven’t already, then you should have robust policies in place that reference privacy, cookies, etc, and the ability for users to make subject access requests etc.

I can provide more detail if you need it.

[Sala]

@phenomlab After complying with EU rules, the site speed improved lol

[phenomlab]

@Sala said in What's your go to product for site stats?:

After complying with EU rules

What did you use for compliance? There are many guidelines, but some are woefully inadequate and in fact, completely wrong.

[Sala]

@phenomlab I should have shared the backstory before obtaining the proper settings. Yes, a lot of plugins make the claim that they will make your site comply with GDPR, but many don’t. I had to backup my database in order for me to acquire the right one, and then I tried testing a few plugins. This “GDPR Complianz” is what I landed on, and it does everything. Because it is automatic, you, as the administrator, don’t have to do any effort. It creates all cookies in the background during installation and whenever new ones arise, blocking them until the user consent.

[phenomlab]

@Sala good choice. That’s easily the best plugin there is for GDPR compliance under WordPress.

[JAC]

Plenty of good options there, making me edge ever closer to starting up that forum again .

[phenomlab]

@JAC You know you want to… I challenge you to resist!

[phenomlab]

For anyone else coming here and is struggling to get pm2 to work with Umami (as I did - it started, but never seemed to work after a reboot which is pretty useless), you can use the below. Obviously, change the parts noted inside the [brackets]. Follow the below instructions:

Instructions

Open a terminal and create a new systemd service file:

sudo nano /etc/systemd/system/umami.service

Add the following content to the file:

[Unit]
Description=Umami Analytics Server
After=network.target
 
[Service]
Type=simple
User=[umami user]
WorkingDirectory=[path to umami]
ExecStart=/usr/local/bin/node [path to umami]/node_modules/.bin/next start
Restart=on-failure
 
[Install]
WantedBy=multi-user.target

Replace [umami user] with the username of the user that should run the Umami service, and [path to umami] with the actual path to your Umami installation.

Save the file and exit the editor.

Reload the systemd manager configuration:

sudo systemctl daemon-reload

Enable the Umami service to start on boot:

sudo systemctl enable umami.service

Start the Umami service:

sudo systemctl start umami.service

You can check the status of the service with:

sudo systemctl status umami.service

This systemd service file will ensure that Umami starts automatically when the system boots, and it will restart the service if it fails. Remember to adjust the WorkingDirectory and ExecStart paths according to where Umami is installed on your system, and ensure that Node.js is installed and accessible at /usr/bin/node (or adjust the path to Node.js as necessary).