Package Details: matomo 4.2.1-1

Git Clone URL: (read-only, click to copy)
Package Base: matomo
Description: A real-time web analytics platform
Upstream URL:
Licenses: GPL3
Replaces: piwik
Submitter: freaknils
Maintainer: C0rn3j
Last Packager: C0rn3j
Votes: 33
Popularity: 0.091861
First Submitted: 2018-04-01 09:31
Last Updated: 2021-03-01 08:16

Dependencies (5)

Required by (0)

Sources (2)

Latest Comments

1 2 3 4 5 6 ... Next › Last »

schickel commented on 2021-01-31 18:19

@navara sadly, no change for this.

I've installed matomo for testin in a virtual host in a seperate directory and there it works fine. So this is really strange....

navara commented on 2021-01-29 11:04

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.

schickel commented on 2021-01-28 18:58

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)

C0rn3j commented on 2020-11-27 10:20

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

If you're updating to 4.0.1 and not a later version, you will most likely run into this and possibly this

C0rn3j commented on 2020-06-09 06:52

You need to import the public key before installing.

gpg --recv-keys B5DBD5925590A237

dest4 commented on 2020-06-08 21:53

Hello, issue with gpg signature

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

C0rn3j commented on 2020-05-31 14:45

@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.

navara commented on 2020-05-10 22:23

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


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.

C0rn3j commented on 2020-02-10 10:52

As a note, Matomo is currently blocked by decent adblockers via EasyList, workaround here that you possibly have to reapply on every update:

pcmoore commented on 2020-01-22 13:45

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