Q100304: What to do if you see a 'CURL' error when trying to activate your Login-based licensing

Follow

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.

  1. Adding Exceptions to your Proxy Server/ Network security

  2. Enter your Proxy Server details on the Licensing Dialog
  3. Proxy Servers with SSL Interception

NOTE: If you are running Modo (14.0 or earlier) and Mari (4.6v3 or earlier) and see an open ssl error please see the following article: Q100672: Important update on older versions of Modo and Mari with login-based licensing starting June 30th

 

Adding Exceptions to your Proxy Server/ Network security

Currently there is no way to enter your proxy settings in Modo 15, Colorway 5, 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 

 

Enter your Proxy Server details on the Licensing Dialog

Modo 14 and Colorway 4:
The window to enter your proxy details appears if Modo/Colorway has not been able to contact the website after you try to login.

NOTE: The window will not appear if the software can connect to the licensing website.

The window to enter your proxy details appears if Modo has not been able to contact the website after you try to login.  Note that he window will not appear if Modo can connect to the licensing website.

mceclip0.png

Modo 11.0 to 14.0, Mari 6 and Nuke 13.1 and below:

You can enter your proxy server details on the Advanced Options on the Licensing dialog.

proxy_details.PNG

After you enter your proxy details, click on "Back" and then enter your login details. 

 

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

If you are unable to obtain a trial license behind a proxy please contact our sales team directly at sales@foundry.com stating which product you wish to trial and the system ID of the machine you wish to utilise the trial on. 

Information on how to find the system ID of your machine can be accessed via the following knowledge base article:

Q100002: What is the system ID and how do I find it?
NOTE: Non-Commercial and Indie licenses can only be generated via the website, they cannot be issued by sales or support.

FURTHER READING

More information about login-based licensing is available in the following articles:

    We're sorry to hear that

    Please tell us why