You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently tried upgrading from Matomo 4.5.0 to 4.6.1 (via the docker apache image), and discovered I was no longer able to connect to the UI due to 500s.
Upon enabling debug logging, I discovered numerous errors like the following:
I am using Matomo with Google's Cloud SQL, which provides self-signed certificates, so I think I have to use ssl_no_verify = 1 (though I'd love not to use that setting if anyone knows a workaround). Removing this setting, as expected, led to Matomo not being able to connect to the database due to certificate verification issues.
Expected Behavior
I expected Matomo to continue to connect successfully to the database with SSL enabled, but verification disabled.
Current Behavior
Matomo is unable to connect to the database and returns 500.
Possible Solution
I noticed that both PHP and Zend received major upgrades between the two docker images for 4.5.0 and 4.6.1. Perhaps this led to incompatibilities?
4.5.0
➜ ~ docker run -ti matomo:4.5.0-apache bash -c 'uname -a && php -v'
Linux f98aac68bbec 5.11.0-41-generic #45~20.04.1-Ubuntu SMP Wed Nov 10 10:20:10 UTC 2021 x86_64 GNU/Linux
PHP 7.4.26 (cli) (built: Dec 2 2021 14:25:17) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
with Zend OPcache v7.4.26, Copyright (c), by Zend Technologies
4.6.1
➜ ~ docker run -ti matomo:4.6.1-apache bash -c 'uname -a && php -v'
Linux fe5285d4b0d8 5.11.0-41-generic #45~20.04.1-Ubuntu SMP Wed Nov 10 10:20:10 UTC 2021 x86_64 GNU/Linux
PHP 8.0.13 (cli) (built: Dec 2 2021 13:29:44) ( NTS )
Copyright (c) The PHP Group
Zend Engine v4.0.13, Copyright (c) Zend Technologies
with Zend OPcache v8.0.13, Copyright (c), by Zend Technologies
Hi @e0001ed9.
Thanks for the report. Could you maybe try if changing some code solves your issue.
Could you try adding 'ssl_no_verify' => null, to this array definition:
Disclaimer - I only tested this in a local test setup with docker so as not to impact my production deployment, but I can confirm that test setup did exhibit the problem above without your suggested change, then resolved with that fix 🎉
sgiehl
added
Bug
For errors / faults / flaws / inconsistencies etc.
and removed
Potential Bug
Something that might be a bug, but needs validation and confirmation it can be reproduced.
labels
Dec 11, 2021
Totally makes sense @justinvelluppillai - thanks! Since I use Matomo via the official docker images, it wasn't immediately obvious that those other dependencies had changed along with the Matomo version.
justinvelluppillai
changed the title
Undefined constant "SSL_NO_VERIFY" after upgrading to 4.6.1
Fix possible undefined constant exception when using ssl_no_verify
Feb 1, 2022
I recently tried upgrading from Matomo 4.5.0 to 4.6.1 (via the docker apache image), and discovered I was no longer able to connect to the UI due to 500s.
Upon enabling debug logging, I discovered numerous errors like the following:
I am using Matomo with Google's Cloud SQL, which provides self-signed certificates, so I think I have to use
ssl_no_verify = 1
(though I'd love not to use that setting if anyone knows a workaround). Removing this setting, as expected, led to Matomo not being able to connect to the database due to certificate verification issues.Expected Behavior
I expected Matomo to continue to connect successfully to the database with SSL enabled, but verification disabled.
Current Behavior
Matomo is unable to connect to the database and returns 500.
Possible Solution
I noticed that both PHP and Zend received major upgrades between the two docker images for 4.5.0 and 4.6.1. Perhaps this led to incompatibilities?
4.5.0
4.6.1
Steps to Reproduce (for Bugs)
ssl_no_verify
enabled.Context
I'm also using the MySQLi adapter. Here is the database configuration:
Impact - I'm unable to upgrade to 4.6.1 from 4.5.0.
Your Environment
The text was updated successfully, but these errors were encountered: