1

I'm using Intellij IDEA Ultimate 2016.3.4.

File / Settings / Plugins / Install JetBrains plugin... opens up a window named Browse JetBrains Plugins, but the main area of the window, which should AFAIK list the plugins available on the JetBrains repository, only displays a "Nothing to show" message.

I am behind a corporate proxy, so I used the HTTP Proxy Settings... button & dialog box to configure proxy settings. I also used the Check connection button to test the proxy configuration with http://plugins.jetbrains.com/, and it worked fine. The Browse JetBrains Plugins window still remains empty. (I also tried the Reload button.)

Am I getting something wrong?

(Yes, I also know there's a workaround: I can download the plugin, and install it manually. The question is not about the workaround, but the in-application download & install feature.)

Attila Csipak
  • 927
  • 2
  • 14
  • 34
  • Is it possible to check the issue with recent IDEA version? Several similar issues were fixed there. – y.bedrov Feb 15 '18 at 13:37
  • I stated the version number in the first sentence and a tag for a reason. If you know issues that are related to the described phenomenon, post one or more JetBrains issue tracker links as an answer. – Attila Csipak Feb 15 '18 at 14:23
  • 1
    Could you please share idea.log ("Help | Show Log in..") after restarting IDE and reproducing the issue to check exact error? – y.bedrov Feb 16 '18 at 17:30

1 Answers1

0

Based on the comment of y.bedrov, I looked at idea.log, and found several instances of the same SSL certificate related exception:

sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

This error can be reproduced using the Check connection button described above, the important thing is to use https in the URL (e.g. https://plugins.jetbrains.com/).

So this looks like a classic SSL certificate path problem. The tricky part is that the web proxy used touches the certificate chains and replaces the original root certificate with the company's own web proxy certificate. The latter is apparently not trusted by the JVM, so it looks like the solution is to export the web proxy root certificate to a file, then import it into cacerts. This solution is described in several existing blog posts (here's an example, a simple Google search may yield dozens more).

Attila Csipak
  • 927
  • 2
  • 14
  • 34