Legacy Licensing Issues

If you run the legacy products and began seeing licensing failures on or after September 3, 2024, the cause is almost always a firewall rule that allowlists the licensing nodes by IP address rather than by hostname. The legacy products check out their licenses from a pool of cloud-hosted FlexNet licensing nodes. Those nodes run on cloud infrastructure whose underlying IP addresses are not guaranteed to be stable, and on September 3, 2024 the addresses behind the nodes changed. A firewall rule pinned to the old IP addresses silently stops matching at that point, the license checkout can no longer reach a node, and the product fails to validate its license.

The fix — and the configuration that prevents this from recurring — is to allowlist the licensing nodes by their fully qualified domain names (FQDNs) and to permit outbound DNS resolution, rather than hard-coding IP addresses. Resolving the hostname at connection time means your firewall continues to follow the nodes wherever the cloud infrastructure places them.

Licensing node FQDNs

Allow outbound access to the following hostnames in your firewall configuration. Legacy products connect to the nodes over either HTTP (port 80) or HTTPS (port 443), depending on your deployment; allow whichever your installation uses, or both if you are unsure.

HTTP — port 80

HTTPS — port 443

After updating the firewall, restart the affected service and confirm that license checkout succeeds. If failures persist once the FQDNs are allowed and DNS resolution is working, contact support@lumenvox.com with the timestamps and any licensing error messages from your logs.