Closed hathagat closed 5 years ago
did you look at #12 and #16 ? Both are related to SSL issues. The last one may very well be the solution - or not, but I'd appreciate you verify this first :-)
Speaking of #12 I use OpenJDK 1.8 so there souldn't be a problem. Additionally I verified that TLSv1 is activated.
The certificates (whole chain including root CA) are already imported to the Java and the Jenkins Keystores and copied to the following folders
/etc/pki/ca-trust/source/anchors/
/etc/pki/tls/certs/
$JENKINS_HOME/.keystore/
The webservers on both servers use the whole chain like mentioned in #16.
However I don't understand why the logs on the Mattermost server don't show any connection attempts.
They may not show any attempts if the SSL negotiation does not work...
Since this is a recurring issue, I looked for a more generic solution; maybe this is something to try? https://support.cloudbees.com/hc/en-us/articles/217309497-Test-a-SSL-connection-from-Jenkins
I just wonder because every other connection between the two servers works as ecxpected.
Thanks for the link! I set up the pipeline and did some testing. There seem to be handshake problems with TLSv1.2. I will investigate further...
Did you find anything that still points at this plugin?
I will close this for inactivity
Hi,
in my environment Jenkins and Mattermost (GitLab Omnibus) are running on two different servers (CentOS, OpenJDK 8, no Docker) with self signed certificates. I added the certificates to the JKS and the appropriate Mattermost, Jenkins and OS folders on both servers.
Jenkins Settings:
When I run the connection test in the Jenkins log shows the following:
The gitlab_mattermost_access log shows nothing in this case.
Testing from Jenkins server using curl works as expected:
curl -i -X POST -d 'payload={"text": "Hello\nText"}' https://mymattermost.local:8066/hooks/123xyz
Here the gitlab_mattermost_access log shows"POST /hooks/123xyz HTTP/1.1" 200 2 "" "curl/7.58.0"
Any idea why the connection fails? Thanks in advance!