SUMMARY
Flix is licensed via RLM licensing in a similar way to other Foundry applications, with a few small differences. Information about installing and troubleshooting Flix licenses can be found below.
MORE INFORMATION
Flix has 2 separate applications: a Flix server and a Flix client. The Flix server holds all the images and metadata associated with them. The Flix client is the application that users use to see and import images. The Flix server is licensed with a license generated by the Foundry. The license can be node-locked or a floating license. Part of that license contains information on how many users can use Flix at the same time. The Flix users (who use the Flix client) don't need to enter any licensing information, as the Flix server knows about the maximum number of users allowed to connect at the same time.
What type of license do you need?
For setups with a single Flix Server, all you need is a node-locked license for the Flix Server machine.
If you’re running multiple Flix Servers, then we recommend using a floating license, with the number of floats equal to the number of Flix Servers running together. One of the Flix Server machines can act as the license server, or you can use a dedicated license server.
The difference between node-locked and floating licenses is explained in the following article: Q100266: What is the difference between Nodelocked, Floating and Login licenses?
Installing Flix licenses
The steps to install Flix licenses are the same as those for other Foundry licenses, but you only need to license the Flix Server machine(s).
Instructions on how to point a Flix Server to a license server in your Flix config can be found in the Flix User Guide.
Troubleshooting Flix Licensing Issues
If your Flix server doesn't start and you see licensing errors, the common issues are:
- Flix can't communicate with the license server. This can be caused by network issues, license server issues, or incorrect licensing configurations in the Flix server's config.yml file.
- The Flix license has expired. You can find the license expiration date in the Flix license file.
- A licensing subprocess is running from an old Flix server version. The best solution for this is to restart the machine, or you can search for and kill all processes with flix in their name.
- Flix can't connect to the licensing subprocess. The licensing subprocess runs on port 8383. It needs to be accessible only from the local flix_server application. We recommend blocking all internet traffic to that port. Restarting the machine can fix problems with communication to the Flix licensing subprocess.
If you see licensing errors when users try to log into the Flix client, or other users lose their connections to Flix, most likely you are running out of user licenses. You can use the Flix licensing tool to check who is using those licenses and return (revoke) any licenses that shouldn't be in use. You can learn how to setup and use the Flix licensing tool from the following KB article: Q100605: How to use the Flix licensing tool to manage usage
If you have other licensing problems with Flix, please search the Support Portal for the licensing error message. If you cannot find a solution to the problem, then please open a support ticket and include the following information:
- A screenshot or copy of the error message when launching Flix
- A Diagnostic file from the Foundry Licensing Utility (FLU) on the Flix Server machine(s) and the license server if you’re using a floating license.
Q100105: How to generate a license diagnostic log via the FLU for troubleshooting license issues
FURTHER READING
In the Foundry learning portal, you can find the Flix User Guide and instructions on how to install the Flix server.
The Foundry Licensing User Guide is available at Foundry Licensing User Guide.
We're sorry to hear that
Please tell us why