SYMPTOMS
When trying to install a Login license you may see an error similar to the following stating that your ‘Token is invalid’.
CAUSE
When you activate your license on a machine via Modo 15, Mari 7, or Nuke 13.2v1 or above, a token license is installed to one of the following directories:
Windows: C:\Users\<USERNAME>\AppData\Local\Foundry\Tokens
OSX: /Users/<USERNAME>/Library/ApplicationSupport/Foundry/Tokens
Linux: $HOME/.local/share/Foundry/Tokens
NOTE: After two decades of 3D workflow innovation, we have made the difficult decision to discontinue Modo, following the release of 17.1. More information on this can be found here
For Individual Login licenses, when you run the program again, if it has an internet connection, it will connect to the website to check it is still valid and then get a new 37 day license. More information on this can be found here: Q100282: What is login-based licensing and which products is it available for?
NOTE: If you are using Nuke versions released prior to May 20th 2025, and you encounter a licensing expiry warning in the licensing dialogue, please refer to the following article:
Q100722: Advisory on resolution of Individual Login-based licensing expiry warnings
As for Teams Login licenses, the token is only temporarily stored in the mentioned directories when the product is in use. Closing the program will remove the generated token license.
NOTE: If you are using Nuke versions released prior to May 20th 2025, and you encounter failed checkout errors when attempting to launch Nuke with a Teams Login license, please refer to the following article:
Q100721: Advisory on resolution of Teams Login licensing system errors
When you see an invalid token error message this means that something within that Token folder is expired or incorrect.
This can happen for a number of reasons but following the steps outlined in the following article will ensure that any old expire tokens are cleared out for you and should help resolve the issue in most cases: Q100285: Initial steps to help solve issues with Individual Login licensing
However, you may still see the error, even if you are completing a fresh license install. When this happens, the following errors are usually located within the licensing logs:
[TokenEntry] Signature verification failed
[TokenEntry] token verification failed: token expired
This can happen if the system time on your machine is incorrect by as little as 5 minutes.
SOLUTION
In order to resolve this issue please follow these steps:
- Check your system clock against an online time source (for example https://time.is/ or https://www.worldtimeserver.com/) .
- Update the system clock on your machine if it is ahead or behind by more than 5 minutes.
- INDIVIDUAL LOGIN LICENSES ONLY Follow the steps outlined in the article below to remove any old licenses: Q100285: Initial steps to help solve issues with Individual Login licensing.
-
Re-activate your license on your device:
Q100585: How to activate your Individual Login license
Q100660: How to activate your Teams Login license
This should then allow you to access the license.
If the System date has been previously changed, correcting the time/date alone may not be enough to resolve the issue. Please follow the steps outlined in the following article if you are still experiencing issues: Q100217: How to resolve the "Clock setback detected" error message
FURTHER HELP
If you are still experiencing difficulties please create a support ticket to let us know the exact issue encountered and the troubleshooting steps that have been taken.
For more information on how to open a support request, please refer to this article: Q100064: How to raise a support ticket
We're sorry to hear that
Please tell us why