Closed dr0i closed 5 years ago
Fixed by generating a self-signed SSL certificate on our proxy server, install and configure it in the vhost, copying this same certificate to the matomo server, install and configure it also there.
Also important entry from vhost-entry of the lobid-server:
ProxyPreserveHost On
.
"Git pushed" vhosts.d/matomo.lobid.org.
Tested, know URI works.
Assigning @acka47 to also check.
(note: letsencrypt-certificates must be renewed every few months. To do this automatically, the CAA record authority must allow that. Asked our domain-owner to allow it, but am not confident that they will agree).
Ah, and the URL has changed. It starts with https://matomo.
It works again, at least from inside hbz.
Matomo at lobid is not working. May be a problem with an outdated letsencrypt ssl certificate.