Licensing server

Flair 1.1.5

Table of contents
  1. Setup
    1. Adding firewall rules
      1. On Linux
      2. On Windows
  2. Troubleshooting
    1. Test communication with Relay
      1. On Linux
      2. On Windows (PowerShell)
    2. Setting a hostname
      1. On Linux (RHEL 7+)
      2. On Windows

A licensing server can be used to Relay Flair licenses through a local network, floating the licenses between artists when needed. These licenses work well when artists need to share licenses or in air-gapped or otherwise offline environments.

Floating licenses are available when purchasing multiple Flair STUDIO or INDIE for Education licenses. Get in touch with our sales team for more information on purchasing floating licenses.

Setup

Once you receive the Flair Relay files from us, follow the steps below to setup the licensing server.

  1. Make sure the server has a human-readable hostname or a static IP address within your network
  2. Extract the Flair Relay files into a folder on the server machine.
  3. Open that folder within the Terminal or PowerShell.
  4. Run ./relay serve to start the floating license sever.
  5. (Optional) Relay will be served on port 6349 by default. To define a custom port, serve by specifying the port: ./relay serve --port ####.
  6. Open another Terminal/PowerShell in the same folder and run ./relay ls --plain to check the status of the server.
The available licenses are listed by running: ./relay ls

Adding firewall rules

Relay will need to be permitted through the firewall of the server machine for computers on the network to connect to it. Contact your network administrator so that they can configure the firewall for your environment.

Below are some basic instructions for Linux (Rocky 9) and Windows, but these may be quite different depending on how your environment is setup.

On Linux

  1. Check what firewall zone your Linux server is operating in

    1

     firewall-cmd --get-active-zones

  2. (Optional) Change the zone your Linux server is operating in for your interface (which you know from the previous command).

    1

     sudo firewall-cmd --permanent --zone=work --change-interface=eth0

  3. Run this command to allow incoming traffic on the relay port for your configured zone (work in this case)

    1
2

     sudo firewall-cmd --permanent --zone=work --add-port=6349/tcp
 sudo firewall-cmd --reload

On Windows

Add a program exception

  1. Go to Settings → Privacy and Security → Windows Security → Firewall and Network Protection
  2. Click on Advanced Settings
  3. Navigate to Inbound Rules and click on New Rule...
  4. Select Program and click on Next >
  5. Choose This program path: , Browse... to the folder where relay is located and double-click on relay.exe. Click on Next > to continue.
  6. Choose Allow the connection and click on Next >
  7. Select all the checkboxes that apply to the rule. Domain, Private, and Public and click on Next >
  8. Specify a name for the rule e.g., Flair Server and click on Finish to complete the process

Troubleshooting

Test communication with Relay

Once the relay server is running, you can check if it is reachable with curl

On Linux 

1

curl -v -X GET "http://SERVERNAME:PORT/v1/health"  # HTTP/1.1 200 OK

On Windows (PowerShell) 

1

& curl.exe -v -X GET "http://SERVERNAME:PORT/v1/health"  # HTTP/1.1 200 OK

If host cannot be reached, check your firewall configuration and enable the necessary ports.

Setting a hostname

On Linux (RHEL 7+)

Run the following command where NEW-HOSTNAME is the new hostname of the server

1

sudo hostnamectl set-hostname NEW-HOSTNAME

On Windows

  1. Open Settings (Win + I)
  2. Go to System > About
  3. Click Rename this PC
  4. Enter a new name and restart your computer