Closed davidfm closed 8 years ago
Hi,
We use the requests
library, that handles certificate verification : http://docs.python-requests.org/en/master/user/advanced/#ssl-cert-verification
requests
checks against a bundled list of certificate authorities, yours might not be in that list.
You can make it use a different/newer list by running pip install certifi
.
If it still fails, can you try running in python requests.get("https://yourmattermostinstance")
, and adjust the optional parameter verify
to a working value (False/True/path to a folder containing CA authorities)?
certifi
changed a few months ago, and no longer supports the verification for 1024-bit certificates. If that's your case, you can try with verify=certifi.old_where()
.
verify=False
did the trick. Thanks!
Hi, I've posted my problem on the Mattermost forum but got no reponses. Hopefully you can give us some pointers on how to fix our issue.
Based on the instructions here I created my own docker container.
When I connect GitLab with this container and click on
Test webhook
it seems to work OK,I see the following on the log:
10.0.0.19 - - [30/May/2016 15:48:02] "POST /new_event HTTP/1.1" 200 -
However, when I add an actual comment it fails and I see the following:
Mattermost is behind a reverse proxy and we use a SSL certificate, but it's not self-signed.
Any ideas on what I am doing wrong?
Many thanks.