Skip to main content

Firewall or proxy allowlist for IntelliJ-based IDEs: required hosts and ports

Jerome Guan
Updated

Question

  • Which hosts and ports must a company firewall or proxy allow for IntelliJ IDEA and other IntelliJ-based IDEs?
  • What is the IP allowlist of IntelliJ-based IDEs?

Answer

JetBrains does not publish IP ranges. The hosts below run on content delivery networks, and their addresses change: in one test session, plugins.jetbrains.com resolved to three different addresses. Allow the hosts by name (FQDN or TLS SNI rules), not by IP address.

All connections use HTTPS on TCP port 443.

Host Used for Needed for
www.jetbrains.com IDE update check (/updates/updates.xml), service configuration files (/config/) Every IDE
account.jetbrains.com License check JetBrains Account licenses
oauth.account.jetbrains.com JetBrains Account sign-in JetBrains Account licenses
frameworks.jetbrains.com Remote IDE configuration (requested about once a minute), Java framework dependency configurations, JetBrains AI configuration Every IDE
download.jetbrains.com IDE resource files, IDE and Toolbox App downloads Every IDE
download-cdn.jetbrains.com IDE resource files, IDE and Toolbox App downloads Every IDE
download-cf.jetbrains.com Downloads. Not contacted in the test below Downloads
plugins.jetbrains.com Plugin search, plugin update checks, plugin suggestions Plugins
downloads.marketplace.jetbrains.com Plugin files: every plugin ZIP downloads from this host Plugins
resources.jetbrains.com Usage statistics configuration Usage statistics
cloudconfig.jetbrains.com Settings storage Backup and Sync
JetBrains AI hosts AI Assistant and Junie. The IDE contacts api.jetbrains.ai and api.jetbrains.cloud at startup, also when AI is not in use JetBrains AI: the full host list is in How to allow access to JetBrains AI Assistant/Junie in the company network firewall/proxy

A custom plugin repository, configured in Settings | Plugins, adds its own host. Plugins and product-specific features can contact other hosts.

Wildcard rules

A *.jetbrains.com rule covers every host in the table except the JetBrains AI hosts on other domains: api.jetbrains.ai, api.jetbrains.cloud, api.app.prod.grazie.aws.intellij.net, and api.ai.jetbrains.com.cn for China. Each of them needs its own rule.

Firewalls that filter by IP address only

Route the IDE through a proxy that filters by host name. Configure the proxy in Settings | Appearance & Behavior | System Settings | HTTP Proxy. By default, the IDE uses the system proxy settings.

How the list was checked

The list was checked against IntelliJ IDEA 2026.2.3 (build 262.10968.63) on Windows 11 in October 2026. The test recorded every connection of the IDE process and every URL in the IDE log. It covered startup, Help | Check for Updates, plugin search and installation, and turning on Backup and Sync. JetBrains Account sign-in was not part of the test: oauth.account.jetbrains.com comes from the JetBrains AI article.

For the IDE Services server, see Network Access Requirements in the IDE Services documentation.

TLS-inspecting proxies

A TLS-inspecting proxy, such as Zscaler or Netskope, can break plugin installation even when the hosts are on the allowlist. The proxy scans the plugin ZIP during the download, then resets the connection or truncates the file. The IDE then reports an error such as:

Plugin "<name>" was not installed: Cannot download 'https://downloads.marketplace.jetbrains.com/files/...': Connection reset
, response: 200 OK

response: 200 OK means that the request succeeded and the connection was reset during the file transfer. The cause is file inspection, not certificate trust. Exclude plugins.jetbrains.com and downloads.marketplace.jetbrains.com from SSL inspection and from file or archive scanning, not only from URL filtering.

If inspection stays on for other JetBrains hosts, the IDE must trust the proxy's root certificate. See How to troubleshoot "Untrusted Server Certificate Warning" and IDE cannot update/download plugins due to firewall/VPN/network threat protection policy.

Troubleshooting

If the problem persists, collect the logs with debug information and send them to JetBrains Support through Help | Contact Support...:

  1. Add the HTTP request categories in Help | Diagnostic Tools | Debug Log Settings.
  2. Reproduce the problem.
  3. Collect the logs with Help | Collect Logs and Diagnostic Data.

Comments

0 comments

Please sign in to leave a comment.