Skip to content

Matomo stack documentation


Use the following credentials during the initial setup on the Database Setup step:

  • Database Server: matomo
  • Login: matomo
  • Password: Copy the value of MYSQL_PASSWORD from [Instance] > Stack > Database page
  • Database Name: matomo


Since version 0.6.0 Matomo comes with GeoIP 2 databases. On Matomo settings page go to Geolocation under System, choose option GeoIP 2 (Php) and click save.


You can customize matomo settings by editing config/config.ini.php file from the SSH container. After the initial release you may not have permissions to do so, to fix that, you just need to redeploy your stack from [Instance] > Stack > Operations page.

Redis integration

You can use redis to store Matomo cache (by default stored in the local filesystem):

  • Enable redis service in your application stack from [Instance] > Stack page
  • Copy your instance UUID from [Instance] > Settings page
  • Access the server hosting your matomo instance as root and append /srv/wodby/instances/[INSTANCE UUID]/app/config/config.ini.php file with the following values:
backend = chained

backends[] = array
backends[] = redis

host = "redis"
port = 6379
timeout = 0.0
password = "Copy the value of `REDIS_PASSWORD` from `[Instance] > Stack > Redis page`"
database = 14

Mail delivery

Go to Settings > System > General settings > Email server settings in your Matomo instance. Specify opensmtpd as server address and 25 as port. For more details how to configure guaranteed email delivery see OpenSMTPD stack documentation

No delivery guarantee

If you're using a server from a public cloud there's a good chance that its IP is already compromised and blacklisted by major mail services, hence your emails will not be delivered or will land in the spam folder. We strongly recommend using OpenSMTPD in pair with a third-party SMTP services.


By default we run the following cron command from crond container every hour:

/usr/local/bin/php /var/www/html/console core:archive --url=${WODBY_URL_PRIMARY}



Environment variables

Variables availability

Environment variables (except ones provided by Wodby) won't be available in PHP-FPM because we set PHP_FPM_CLEAR_ENV=yes by default for security reasons. You can set it to yes to make all environment variables available in your code.

In addition to global environment variables, we provide the following variables in PHP container that you can use in your post-deployment scripts or settings files:

Variable Description
$APP_ROOT /var/www/html by default
$HTTP_ROOT e.g. /var/www/html/web
$CONF_DIR /var/www/conf by default
$WODBY_HOSTS [ "", "" ]

Deprecated variables:

Variable Instead use

Files directory permissions

Public files directory (symlink to /mnt/files/public) that used for uploads owned by www-data user (PHP-FPM user) by default and the default container user (wodby) has no writing permissions. So if you run a command that creates files in a public directory you will get insufficient permissions error. You can fix this problem by giving writing permissions for files directory to the owner's group (user wodby is a member of www-data group) by using one of the helper scripts:

sudo files_chmod /mnt/files/public

When you manually import files under wodby user you should change files ownership to www-data user to let PHP-FPM create new files in directories, run the following command to change the ownership:

sudo files_chown /mnt/files/public

Helper scripts scope

files_chmod and files_chown are the only sudo commands available to wodby user and can be applied only to directories under /mnt/files .

For mode details about users and permissions in PHP container see

Codebase directory permissions

The codebase owned by the default wodby (uid/gid 1000) user. If you need to give writing permissions to PHP-FPM (www-data user with uid/gid 82) to a directory outside on public files directory you can either access a container as root user or change it from the host server (single-server infrastructure):

chown -R 1000:82 /srv/wodby/instances/[INSTANCE_UUID]/app/path-to-directory
chmod -R 775 /srv/wodby/instances/[INSTANCE_UUID]/app/path-to-directory


A duplicate of the main PHP container runs with crond (instead of FPM). You can customize crontab from [Instance] > Stack > Settings page.

$WODBY_HOST_PRIMARY is a domain marked as primary.


A duplicate of PHP container runs with SSH daemon (instead of FPM). You can find access information on [Instance] > Stack > SSH

Public SSH keys from your Wodby profile will be added automatically for all users that have access to an instance.





This changelog is for Matomo stack on Wodby, to see image changes see tags description on repository page.


⬆️  Matomo 4.3.1


⬆️  Matomo 4.2.1


Added Matomo v4


  • ⬆️  Base image Alpine Linux updated to 3.12.3
  • 🦴  ImagePullPolicy changed to IfNotPresent


Matomo 3.14.1


Matomo 3.14


Matomo updated to 3.13.6


Matomo updated to 3.13.5


Matomo updated to 3.13.4


Matomo updated to 3.13.0


Matomo updated to 3.12.0


  • Matomo updated to 3.11.0
  • Bugfix: crond service missed preloaded icon library


Bugfix: duplicated Nginx services (missing version 1.16)


Bugfix: default Nginx service version had an incorrect preset that caused 403 Forbidden error.


  • Matomo updated to 3.10.0
  • Adminer updated to 4.7.2
  • Alpine Linux updated to 3.10.1


  • Matomo and Adminer rebuilt against the latest PHP image
  • Added new Nginx versions 1.17, 1.16


  • Matomo and Adminer rebuilt against the latest PHP image
  • Nginx:
  • Alpine Linux updated to 3.9.4


  • Matomo and Adminer rebuilt against the latest PHP image
  • Nginx:
  • Alpine Linux updated to 3.9.3 for Matomo, Adminer, MariaDB, Redis, OpenSMTPD


Matomo updated to 3.9.1 and rebuilt against the latest PHP image


Matomo updated to 3.8.1 and rebuilt against the latest PHP image


  • Matomo updated to 3.8.0 and rebuilt against the latest PHP image
  • We now fix permissions for config/config.ini.php so you can customize settings from SSH container
  • GeoIP 2 database now included, see how enable geolocation


  • Matomo updated to 3.7.0 and rebased on the latest PHP image
  • MariaDB:
    • Patch updates: 10.3.11, 10.2.19
    • We now run mysql_upgrade automatically on stack upgrades
    • Import action now allows *.mysql files
  • Redis patch updates: 5.0.3, 4.0.12
  • Nginx patch updates: 1.15.7, 1.14.2
  • Adminer updated to 4.7.0 and rebased on the latest PHP image


  • Matomo rebased on the latest PHP image
  • Added Redis 5
  • Nginx:
    • Patch updates: 1.15.6, 1.14.1
    • Nginx now uses real IP set from Edge
    • Bugfix: txt was missing from the default list of static extensions


Matomo patch update: 3.6.1


  • Matomo rebased to the latest stable PHP image
  • Adminer:
    • Bugfix: some $PHP_ env vars were ignored
    • Default memory limit set to 512M
    • Adminer and Webgrind rebuilt against the latest PHP image


  • Matomo rebased to the latest stable PHP version
  • Added Adminer service


Matomo rebased to the latest stable PHP version


PHP security updates


Minor Nginx fixes


  • Matomo image updated to the latest PHP image
  • Minor Nginx fixes


  • Matomo updated to 3.6.0
  • Patch updates for PHP, Nginx and MariaDB


  • Matomo updated to 3.5.1
  • Added Nginx 1.14, 1.15
  • MariaBD:
    • Added new version 10.3
    • Version 10.2 updated to 10.2.15
    • Default innodb_buffer_pool_size set to 128M that should significantly decrease memory usage
  • PHP error reporting now exludes strict and deprecated errors


  • Matomo updated to 3.5.0
  • Added SSHD container
  • Matomo image rebased to latest stable PHP 7.1 image (wodby/php:7.1-4.4.2)


  • Bugfix: cron task failed


  • PHP updated to 7.1.15 (security updates)
  • Redis service added
  • Docs: added instructions for redis and email configuration
  • Bugfix: insufficient permissions for plugins install


  • Initial release