Cannot connect via HTTPS proxy for license check with IntelliJ Idea2017.3
I recently re-activated my license for Idea2016.1 (ideaIU-2016.1.1) without issue. I then downloaded the current version, Idea2017.3 (ideaIU-2017.3.2). I imported my settings from Idea2016.1 but when I try to activate my Idea2017.3 I get this error:
INFO - .license.impl.JetprofileSource - Unexpected JBA connection error: java.io.IOException: JetBrains Account connection error: Received fatal alert: access_denied
INFO - .license.impl.JetprofileSource - Received fatal alert: access_denied
And a dialog saying that I may behind a proxy (I am) and that I need to update my HTTPS proxy settings. I've tried several times but I can't get past this error.
What's confusing me is that Idea2016.1 was able to reach the license server (activating by account) with the same settings.
I noticed 2017.3 has a newer JDK (though both 2016.1 and 2017.3 both use JDK 1.8.0... so, maybe unrelated)
Any help would be very appreciated!
请先登录再写评论。
You may need to install the self signed certificates used by the proxy into the JVM keystore of the Java runtime that is used to run IntelliJ IDEA. See https://intellij-support.jetbrains.com/hc/en-us/community/posts/115000094584-IDEA-Ultimate-2016-3-4-throwing-unable-to-find-valid-certification-path-to-requested-target-when-trying-to-refresh-gradle?page=1#community_comment_115000405564.
Or there could be some change on your proxy that blocks requests from IntelliJ IDEA.
I have same problem. When I try to activate IntellijIDEA 2017.3.2 then I see the error: JetBrains Account connection error: www.jetbrains.com. I don't think that it's about proxy, because my Intellij IDEA can check new updates.
IDEA log:
2018-01-11 08:59:43,120 [ 235432] INFO - .license.impl.JetprofileSource - Unexpected JBA connection error: java.io.IOException: JetBrains Account connection error: www.jetbrains.com
2018-01-11 08:59:43,137 [ 235449] INFO - .license.impl.JetprofileSource - www.jetbrains.com
You have a different problem which is a recent regression, see https://youtrack.jetbrains.com/v2/issue/IDEA-184336 for the workaround.
You're right. It works. Thank you.