Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add config option to use own cacert.pem file #14113

Merged
merged 3 commits into from May 5, 2019

Conversation

fdellwing
Copy link
Contributor

@fdellwing fdellwing commented Feb 18, 2019

Fixes #13742

  • Add blog or FAQ article describing the problem and this new solution

@tsteur
Copy link
Member

tsteur commented May 2, 2019

Looks good in general @fdellwing

I reckon it could be good to mention in the config comment when someone would want to adjust this and for what it is used.

@fdellwing
Copy link
Contributor Author

What do you think of? An explanation what file Matomo uses by default, where is comes from and what it does?

@tsteur
Copy link
Member

tsteur commented May 2, 2019

I reckon it be useful to know what the cert is used for, and what use case there is for someone to change it. Like we would someone ever want to change it? Could there be some simple example or so maybe?

@fdellwing
Copy link
Contributor Author

Please take a look now :)

Copy link
Member

@tsteur tsteur left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome 👍 I'll merge next week and then fix ui test

…Instance()->General['custom_cacert_pem'] directly on some systems

shouldn't be an issue anymore, but better be safe.
@tsteur tsteur merged commit 0e04562 into matomo-org:3.x-dev May 5, 2019
@tsteur
Copy link
Member

tsteur commented May 5, 2019

@fdellwing if you did want to write an FAQ let me know and I'm happy to publish it. Otherwise they mind find the issue and pull request here by searching on the web

@fdellwing fdellwing deleted the config_cacert branch May 6, 2019 07:07
@fdellwing
Copy link
Contributor Author

@tsteur Is this ok for the FAQ? Should be in the troubleshooting section I guess.

I get: "curl_exec: Peer’s Certificate issuer is not recognized… Hostname requested was: plugins.matomo.org"

This message will appear if you use a firewall or proxy server that breaks SSL connections and reencrypts them afterwards with its own certificate. Matomo uses a cacert file extracted from the Firefox browser and is therefore unable to connect to any SSL encrypted page with your specific setup.

To solve this issue you are able to provide your own cacert file that trusts your proxies certificate. To use your own file add custom_cacert_pem = "/path/to/your/cacert.pem" to the [General] section of your config. Make sure the file is readable by your webserver.

@tsteur
Copy link
Member

tsteur commented May 9, 2019

Awesome, thank you! Published https://matomo.org/faq/troubleshooting/faq_34226/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Document the use of a matomo specific cacert.pem and allow to disable this behaviour
2 participants