SUMMARY
If you are connected to the internet behind network security or through a proxy server this may prevent our software from connecting to the Foundry website to activate a license on your machine.
You may see an error similar to this:

Fortunately, there are a few ways you can workaround this.
-
Adding Exceptions to your Proxy Server/ Network security
- Proxy Servers with SSL Interception
NOTE: As of April 30th 2025, Login licenses are no longer available for Modo 14.2 and earlier, and Mari 6.0 and earlier. If you are using these versions of Modo and/or Mari, and are encountering issues, please see the following article:
Adding Exceptions to your Proxy Server/ Network security
Currently there is no way to enter your proxy settings in Modo 15, Mari 7 & Nuke 13.2v1 and above via the license UI. In order to add an exception in your proxy you will need to do this outside of the application.
Website URL:
If your proxy server/ network security blocks all outgoing communication except allowed addresses then you should be able to activate your login-based license by adding the following address to the allowed list:
- https://id.foundry.com/
-
https://licenceapi.foundry.com on port 443
Environment variables:
You can set your proxy information outside of the license UI via environment variables. Please set the following environment variables on your machine, these map directly to Curl library settings:
FN_CURLOPT_PROXY maps to CURLOPT_PROXY
see https://curl.se/libcurl/c/CURLOPT_PROXY.html
FN_CURLOPT_PROXYUSERPWD maps to CURLOPT_PROXYUSERPWD
see https://curl.se/libcurl/c/CURLOPT_PROXYUSERPWD.html
Proxy Servers with SSL Interception
If your proxy server has SSL interception then the software will fail to get a license and return "CURL error: (35) SSL connect error" as an error message.
You can work around this by setting an environment variable to tell the software where it can find the certificate file for your proxy server. The variable is called FN_LICENSE_CERTIFICATE and you need to set it to the location of the certificate file. If you're unsure of where the certificate file is then please speak to your system administrator.
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
Information on how to find the System ID of your machine can be accessed via the following article:
Q100002: What is the System ID and how do I find it?
FURTHER READING
More information about Login licensing is available in the following articles:
- Q100282: What is Individual Login licensing and which products is it available for?
- Q100285: Initial steps to help solve issues with Individual Login licensing
- Q100286: How to manage your Individual Login licenses
- Q100585: How to activate your Individual Login license
- Q100586: How to deactivate your Individual Login license
We're sorry to hear that
Please tell us why