SYMPTOMS
When attempting to launch Nuke with a Teams Login-Based license, the following errors may be displayed in the Nuke Licensing dialog:
NOTE: You may encounter various errors, some of which may reference specific product names.
CAUSE
On the 18th of May, 2025, a required server-side change to our licensing system affected communication between our products and the server. As a result, Team license checkouts failed even when valid licences were available.
This issue only affected Team licenses for the compatible Nuke family products on all operating systems; other Foundry products and licensing types were not impacted.
To prevent similar issues in the future, we are reviewing our deployment processes to ensure that changes are tested against supported versions. We will also review client/server communication to increase robustness to server side changes, and additional safeguards will be introduced to detect and isolate future potential compatibility issues earlier in the lifecycle.
RESOLUTION
We’ve now released updated versions of Nuke that resolve this issue. If you are able to upgrade, we recommend downloading and installing one of the following Nuke family product versions:
NOTE: Before using the new versions or implementing the workaround below, please remove the temporary RLM workaround licenses provided during the outage. More information on how to do that can be found here: Q100257: How to remove licenses from your machine
WORKAROUND
If you are unable to upgrade to the latest versions of the Nuke family products at this time, you can use a workaround by setting the FN_CURLOPT_CAINFO environment variable to point to a newer Nuke certificate bundle file.
NOTE: You will need to remove any existing licensing tokens before setting this environment variable.
Please follow the steps in the following articles to apply the work around: Q100720: How to work around login-based licensing issues without upgrading to the latest Nuke versions
FURTHER HELP
If you are still seeing any issues after performing the steps outlined in this article, then please open a Support ticket and let us know the issue you are encountering and the troubleshooting steps you have taken so far, including a screenshot of any error messages.
For more information on how to open a Support ticket, please refer to the Q100064: How to raise a support ticket article.
We're sorry to hear that
Please tell us why