0.34.0 and 0.34.1 fail with "Unsupported or unrecognized SSL message"
See original GitHub issueDescription
After updating the d-m-p to version 0.34.0 the build on our Jenkins Build server fails with
[ERROR] Failed to execute goal io.fabric8:docker-maven-plugin:0.34.1:build (build-start-docker) on project XXX: Cannot create docker access object : Unsupported or unrecognized SSL message
Rolling back to d-m-p version 0.33.0 fixes the build. I also tried with the new release 0.34.1, but it failed as well.
On my local workstation I have no such problems.
The project is not public, so I can’t share a link to it. But if you need more information I should be able to get it.
Info
- d-m-p version : 0.34.0
- Maven version (
mvn -v
) : 3.6.1
- Docker version : Docker version 1.13.1, build 64e9980/1.13.1
- If it’s a bug, how to reproduce :
- If it’s a feature request, what is your use case :
- Sample project : [GitHub Clone URL]
Issue Analytics
- State:
- Created 3 years ago
- Comments:7
Top Results From Across the Web
Unrecognized SSL message, plaintext connection? Exception
I think this is due to the connection established with the client machine is not secure. It is due to the fact that...
Read more >Unrecognized SSL message plaintext connection Exception
I have a java compile package to speak with the https server on the net. Running the compilation gives the following exception:
Read more >fabric8io/docker-maven-plugin
Waiting for a container to startup based on time, the reachability of an URL, or a pattern in the log output. Support for...
Read more >Unrecognized SSL message, plaintext connection?
OldIOSession - An error occurred trying to process a client request. javax.net.ssl.SSLException: Unrecognized SSL message, ...
Read more >FTPS - Unsupported or unrecognized SSL message
I believe that error message is usually when the Java code Mendix is using is expecting encrypted content back, but is instead receiving ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It seems that the commit https://github.com/fabric8io/docker-maven-plugin/commit/dba617ea5137aa9c357ab314cef7ee6e77a80c2b#diff-c9c2f37e986a0ff74e5e7c340ace74e8 on EnvUtil.java is the culprit. See issue https://github.com/fabric8io/docker-maven-plugin/issues/1359 and PR https://github.com/fabric8io/docker-maven-plugin/issues/1360. @rhuss even mentioned that people might be affected 😉 : https://github.com/fabric8io/docker-maven-plugin/pull/1360#issuecomment-667867080
The cause in my case is that the Jenkins build server has a non-standard port in its configuration as docker host:
tcp://myjenkins.domain.tld:4243
. Before the changetcp
was replaced byhttp
, now it’s replaced byhttps
.I guess I’d just have to change the configuration of the Jenkins build server to
http://myjenkins.domain.tld:4243
, as the documentation mentionstcp:
only for ports 2375 and 2376 anyway?I submitted https://github.com/fabric8io/docker-maven-plugin/pull/1613 for covert the tcp protocol to http protocol.