Q100720: How to work around login-based licensing issues without upgrading to the latest Nuke versions

Pete

Updated: May 12, 2026 21:59

Created: January 20, 2026 15:57

SUMMARY

To work around login-based licensing issues after our server-side update, while unable to upgrade to the latest versions of the Nuke family products, you can use the FN_CURLOPT_CAINFO environment variable to point to a newer Nuke certificate bundle file.

MORE INFORMATION

Please follow the steps below to apply the work around completely:

1. Remove any existing licensing tokens by deleting the Tokens folder from the default locations below:

Windows: C:\Users\<USERNAME>\AppData\Local\Foundry\Tokens

macOS: /Users/<USERNAME>/Library/ApplicationSupport/Foundry/Tokens

Linux: $HOME/.local/share/Foundry/Tokens

2. After the Tokens folder has been removed, download the newer certificate bundle from here:

Certificate download

NOTE: The location of the certificate bundle can be set to a network location and using the environment variable, deployed on all machines within your network via your network management software or deployment tool. For that, make sure to place the downloaded certificate bundle in a location that is accessible to all users.

3. Set the FN_CURLOPT_CAINFO environment variable value to the location of the downloaded certificate bundle (ca-bundle.crt).

See the sections below for examples of how to set the environment variable temporarily on a machine:

Windows:

set FN_CURLOPT_CAINFO=<PATH-TO>\ca-bundle.crt

Linux/macOS:

export FN_CURLOPT_CAINFO=<PATH-TO>/ca-bundle.crt

NOTE: To deploy this across all machines within your network using the environment variable, you can set its value to a UNC path, for example on Windows like so:

set FN_CURLOPT_CAINFO=\\<PATH-TO>\ca-bundle.crt

You can set the environment variable temporarily or permanently on the machine you’re planning to run the version of a Nuke family product released before the fix was applied. We recommend setting it permanently if you need to use an older version of Nuke in the future.

NOTE: Setting environment variables permanently ensures that the variable will be available whenever a process calls it, even after the computer restarts and regardless of how the process is launched.

For macOS devices, there are two options for setting the environment variable permanently

Option 1 - Using a preconfigured .plist file

Download the following preconfigured .plist file and copy paste it into ~/Library/LaunchAgents

This automatically sets the FN_CURLOPT_CAINFO environment variable to point to the Nuke certificate bundle desired location on your system: /Users/Shared

NOTE: If the Library folder isn’t visible on your system, you may need to unhide it. To do that, open Finder and press Command (⌘) + Shift + . (period). This will toggle hidden files on or off in Finder.

NOTE: A system notification may display with the following message, confirming the .plist was installed successfully:

Download the Nuke certificate bundle and copy paste it into /Users/Shared
Restart your machine for these changes to take effect.
Once your machine has restarted, launch the version of Nuke family product released before the fix was applied and follow the steps in the Licensing dialog to select Login License > Team > INSTALL > DONE

You should now be able to launch the product as expected.

Option 2 - Setting your own .plist file

Instructions to set the environment variable in a .plist file can be found in the following article under the Setting environment variables permanently section: Q100015: How to set environment variables

4. Launch the version of a Nuke family product released before the fix was applied.

SUMMARY

MORE INFORMATION

FURTHER READING