-
Notifications
You must be signed in to change notification settings - Fork 612
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
JDK 1.8.x javax.net.ssl.SSLException: Received fatal alert: protocol_version #638
Comments
Which java / jenkins / plugin versions are you running? |
On one Jenkins server I am running: The other Jenkin's instance I don't have access to the management console at the moment but I know it it is on Java 1.8.x and github api plugin 1.90. I'm assuming it is the latest ghprb plugin but will verify tomorrow. I was going to try hardcoding the TLS version even though I'm on JDK 1.8 to see if that made any difference. |
@cybo42, how'd it go? We're seeing this issue as well in some instances. |
Fingers crossed, but so far since I hardcoded the TLS version It bothers me that I'd have to do that since JDK 1.8 should default to 1.2. But maybe something is causing it fallback. Maybe a persistent connection or something like that. (grasping at straws) |
@cybo42 |
This fixed it for us, but not sure why the plugin would not use TLS1.2 if that's the default. The non-PR jobs were running fine. |
Thanks so much @cybo42. I'm not sure if there is a better place to put that though. |
Issue seems to be resolved by using latest jdk version or harcoding tls version. |
We've had the same issue. After our Nexus has been moved to TLS 1.2 the Jenkins was not able to connect to it. Restarting Jenkins solved the issue. Our Java Version is "1.8.0_101" |
Starting after Github updated their certificates I started to receive the below error message. Which is very similar to #634. With one exception, I'm running Java 1.8 which should default to TLS 1.2
I've found that restarting my jenkins instance resolves the issue. However it will start up again after some time. Restart always seems to resolve it, but that isn't the ideal solution ;)
This is happening on two of my Jenkins environments each running different jenkins versions. (2.89.2 and 2.21). One is also running on linux, the other on osx.
I'm not sure if the issue is in this plugin or the underline github-api plugin. I do see this ticket:
hub4j/github-api#418
The text was updated successfully, but these errors were encountered: