Arch Linux User Repository

GPG key changed with 4.8.0 release!

You need to import the public key before installing:
gpg --recv-keys F529A27008477483777FC23D63BB30D0E5D2C749

For versions before 4.8.0 you need the old key:
gpg --recv-keys 814E346FA01A20DBB04B6807B5DBD5925590A237

Indeed. This is pretty much always on the screen, running the commands doesn't change it - changes are promoted on the filesystem, yet detection fails.

Matomo couldn't write to some directories (running as user 'http'). Try to Execute the following commands on your server, to allow Write access on these directories:

chown -R http:http /usr/share/webapps/matomo

find /usr/share/webapps/matomo/plugins -type f -exec chmod 644 {} \;

find /usr/share/webapps/matomo/plugins -type d -exec chmod 755 {} \;

It also expects webserver to write into tracking file, but I refuse to allow that (as if writable plugins directory wasn't enough of security threath) and update the tracking js via command line interface.

After installing from AUR, I get the following error:

Matomo couldn't write to some directories (running as user 'http').

After this a list of folders in /usr/share/webapps/matomo/tmp

The message recommended to make a

"chown -R http:http /usr/share/webapps/matomo" and after that "chmod 644" on all folders in /usr/share/webapps/matomo/tmp

This does not help and I didn't found any solution how to fix this.

I'm using: Apache/2.4.46 PHP 7.4.14 (fpm-fcgi)

If you are upgrading Matomo from 3.x to 4.x, you will probably have(supposed to be optional but isn't with current issues in 4.0.1) to manually convert your database after updating via

./console core:convert-to-utf8mb4

as per

https://matomo.org/faq/how-to-update/how-to-convert-the-database-to-utf8mb4-charset/

If you're updating to 4.0.1 and not a later version, you will most likely run into this https://github.com/matomo-org/matomo/issues/16824 and possibly this https://github.com/matomo-org/matomo/issues/16827

GPG key changed with 4.8.0 release!

You need to import the public key before installing:
gpg --recv-keys F529A27008477483777FC23D63BB30D0E5D2C749

For versions before 4.8.0 you need the old key:
gpg --recv-keys 814E346FA01A20DBB04B6807B5DBD5925590A237

Hello, issue with gpg signature

==> Verifying source file signatures with gpg...
    matomo-3.13.6.tar.gz ... FAILED (unknown public key B5DBD5925590A237)

@navara While that override seems to be needed, it should probably not be a part of the package but a mention on the wiki, official packages like Nextcloud do it that way. https://wiki.archlinux.org/index.php/Matomo

Please add file /etc/systemd/system/php-fpm.service.d/override_matomo.conf with this content:

[Service]

ReadWritePaths = /usr/share/webapps/matomo/config

ReadWritePaths = /usr/share/webapps/matomo/plugins

ReadWritePaths = /usr/share/webapps/matomo/matomo.js

Because new restrictions on php-fpm since 7.4, where ProtectSystem is set to full prevent Matomo to function correctly (unable to install plugins, change configuration, etc).

Above fixes the issue while not exposing more then necessary and still allows user to change ACL as described in installation manifest, if he doesn't like that.

As a note, Matomo is currently blocked by decent adblockers via EasyList, workaround here that you possibly have to reapply on every update: https://github.com/matomo-org/matomo/issues/7364#issuecomment-564027185

FYI, v3.13.1 is out now and is marked "critical":

• https://matomo.org/changelog/matomo-3-13-1

I'll try taking care of it for now then, bumped the version to 3.12.