A lot of features in CLion require access to the internet. If you are working offline (for example, in an isolated environment), there are some aspects that you should keep in mind.
By default, CLion is configured to check for updates automatically and notify you when a new version is available. Updates are usually patch-based: they are applied to the existing installation and only require you to restart the IDE. However, sometimes patch updates are not available, and a new version of CLion must be installed.
If CLion does not have HTTP access outside your local network, it will not be able to check for updates and apply patches. In this case, you have to download new versions of the IDE and install them manually as described in Standalone installation.
For more information, see Update CLion.
Usually, plugins are installed from the JetBrains Plugin Repository. However, you can set up a custom plugin repository in your local network and configure CLion to use it for installing and updating plugins.
Alternatively, you can download and manually install plugins from disk.
You can evaluate CLion for up to 30 days. After that, buy and register a license to continue using the product.
If CLion does not have HTTP access outside your local network, you will not be able to use the JetBrains Account for signing in. However, you can generate an offline activation code that will be valid during your subscription term.
If your organization has at least 50 active subscriptions or licenses of JetBrains products, you can use the Floating License Server to activate CLion instances within your company network. Keep in mind that the License Server itself requires internet access for connecting to the JetBrains Account.
For more information, see Register.
Some code inspections verify external resources. For example, the Non-existent web resource inspection highlights dead links. If you don't have internet access, these inspections will not work and dead links will not be highlighted.
For more information, see Static code analysis.
Version control systems
Most likely, your source code is under some sort of version control system (VCS). If a remote repository is not in your local network, and there is no internet access, CLion will not be able to communicate with the VCS. For example, if you are using Git, you will be able to commit your changes but won’t be able to push them to the remote repository or pull updates from it.
For more information about VCS integration, see Version control.
Tasks and issue trackers
If the issue tracker server is not in your local network, and there is no internet access, CLion will not be able to sync your issues. In this case, you will be able to work only with local tasks that you create yourself.
For more information, see Manage tasks and contexts.
By default, Gradle connects to remote repositories and checks for updates on every launch. Resolving Gradle dependencies can require downloading new artifacts. You can switch to offline mode if you want Gradle to use only those resources that are available locally.
Switch Gradle to offline mode
In the Gradle tool window, click .
This will append the
--offline option to all Gradle commands that CLion runs. It will also report any items that cannot be found in the local repository.
Even if you enable anonymous usage statistics, it will not be sent if there is no HTTP access outside your local network. Also, you can disable this feature entirely if you agreed at first and then changed your mind later.
Disable sending usage statistics
In the Settings/Preferences dialog Ctrl+Alt+S, select Appearance & Behavior | System Settings | Data Sharing.
Clear the Send usage statistics checkbox.