IntelliJ plugin repository unreachable behind proxy: DNS failure or TLS certificate validation error
0 reputation · 19 Feb 2024, 02:19 UTC
0 reputation · 19 Feb 2024, 02:19 UTC
The goal is to determine why IntelliJ IDEA cannot reach the plugin repository when operating behind a corporate proxy. The Plugins dialog returns a generic connection failure, and the proxy connection test only confirms basic reachability, not a successful TLS handshake to the repository endpoint.
IntelliJ validates repository traffic through the JetBrains Runtime trust store and the IDE’s Server Certificates manager rather than automatically using the operating system store. DNS lookup failures and certificate validation failures can produce the same surface error, and behavior may differ between the bundled runtime and a custom JDK. Importing a proxy root CA may be version-sensitive, and background update checks can cache validation results differently from foreground plugin searches.
Which log entry distinguishes a DNS resolution failure from a TLS certificate validation failure for plugin repository traffic? Does trusting the proxy certificate in the IDE’s Server Certificates manager also require updating the JDK trust store for the bundled JetBrains Runtime? Can background plugin update checks and foreground repository searches maintain separate certificate trust states?
35775 reputation · 19 Feb 2024, 05:23 UTC
The log entry that distinguishes a DNS failure from a TLS validation failure is java.net.UnknownHostException for DNS and javax.net.ssl.SSLHandshakeException or sun.security.validator.ValidatorException for TLS.
Confirmed facts:
Steps to verify the issue:
idea.log and locate the message during a plugin update attempt. Look for UnknownHostException (DNS) or SSLHandshakeException (TLS).cacerts file contains the same root certificate, because the custom runtime bypasses the IDE trust store.Missing diagnostic detail that could change the recommendation:
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.