​
Supported Versions

Version 2022.3 or greater.

  • JetBrains Fleet or Reshaper are not supported
  • IDEs with remote SSH support require version 2023.3 or greater

​
Gathering extension logs

Starting in extension version 1.10.0, the Chat Panel has an Extension Diagnostics button on the Settings page. This button will automatically collect relevant logs and parameters into a text file that can be downloaded.

For older versions of the extension:

  1. Logs are written to the idea.log file. To locate this file, go to the Help > Show Log in Finder/Explorer menu option

  2. Export or copy the logs

​
How to reset or change your Enterprise URL

  1. Go to Tools → Codeium Enterprise → Reset Codeium Enterprise Updater.

  2. Enter the new URL ensuring no leading or trailing whitespace.

  3. Restart your IDE.

  4. After restarting, you will be prompted to log in.

​
Known IDE issues and solutions

​
Codeium Chat doesn’t work (or Codeium doesn’t work at all)

If the Codeium JetBrains extension isn’t working, a good first step is to try and reset the plugin by going to Help > Find Action > Reset Codeium Enterprise Updater.

If the issue is isolated to a few users, this is likely because the Enterprise Domain URL certificate is not loaded to your IDE. Your team’s admin should know how to do this.

​
Codeium Chat not being displayed

Usually, you will see the following error in the logs:

JCEF is not supported in this env or failed to initialize

JCEF is a browser needed to display Codeium Chat. To fix this, go to Help > Find Actions > Choose Java Boot Runtime and pick a version that has JCEF bundled.

​
Certificate Issues

If you encounter the following errors:

Failed to fetch extension base URL at <YourDomainURL>

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

This suggests that the Codeium extension is unable to trust the TLS connection to your enterprise portal / API server because it does not trust the certificate being presented. This either means that the certificate presented by the Codeium deployment is untrusted or a certificate presented by a corporate proxy intercepting the request is untrusted.

In either case, the most preferable solution is to ensure that the root certificate that signed this certificate is properly installed on end-user machines in the appropriate location. JetBrains IDEs and most other IDEs load certificates from the operating system’s default location.

Your certificate is issued and managed by your local IT or Admin team. Please reach out to them for assistance with installing the necessary certificates on your system.

It is important that the full certificate chain is being presented from wherever TLS is being terminated. Oftentimes, if only the leaf certificate is presented, JetBrains IDE and other IDEs are unable to verify its authenticity because they are not aware of the intermediate certificate which validates the leaf certificate and is validated by the root certificate. Browsers are often able to work around this issue as users will likely have encountered a different website that does present the full certificate chain, so the intermediate cert is seen and cached, but applications like JetBrains IDEs don’t have this advantage.

Note: In JetBrains family products 2024.3 a bug was introduced in which the IDE is failing to accept the OS certificates (JetBrains issue report). To solve this, users can do any of the following:

  • Downgrade JB products to earlier versions
  • Use the 2024.3.1 preview version (beta version)
  • Add -Djavax.net.ssl.trustStoreType=Windows-ROOT as a custom JVM option