License Connection through Proxy

[JeffS (Jeffrey Schaper)]

Our School has a proxy so we cannot connect to the license server. Do you have Windows environment settings we can add to “let the software know” to go through a proxy, i.e. TI software use:

• In the Variable name field, type TI.HttpsProxy.
• In the Variable value field, type : proxy:port

[Rick (Technical Evangelist)]

From our FAQ on Licensing Setup - Configuring different license options

@Rick

Network Restrictions

LightBurn will need to communicate with the external license server to verify licenses. If you are experiencing difficulties with a license not being verified, your network may be restricting this.

Please ensure the following is set up on your network:

Whitelist api.cryptlex.com for port 443

It is also possible to configure LightBurn to access the network through a proxy. You can append the proxy connection address using -p ProxyString

The proxy format is: [protocol://][username:password@]machine[:port]

Examples of valid proxy strings:

• http://127.0.0.1:8000/
• http://user:pass@127.0.0.1:8000/
• socks5://127.0.0.1:8000/

[JeffS (Jeffrey Schaper)]

Thanks Rick, we have whited listed api.cryptlex.com for port 443 but it is still failing. Is there another port that needs to be added to the whitelist?

[Rick (Technical Evangelist)]

@JeffS

whited listed api.cryptlex.com for port 443 but it is still failing

Are you getting a specific error message?

[JeffS (Jeffrey Schaper)]

Yes, “Failed to connect to the server due to network error”. Below is our Wireshark logs

it didn’t like my Wireshark log I tried to attach

[Rick (Technical Evangelist)]

Add .txt to the end of your file and try again please.

[JeffS (Jeffrey Schaper)]

Wireshark.txt (1.3 KB)

[JeffS (Jeffrey Schaper)]

You will notice my computer sees your license server but gets rejected. The floating license we use works on a device if we “tether” the device bypassing the firewall. So it’s not the license key.

[Rick (Technical Evangelist)]

@LightBurn need your help on this.

[coreyammons]

It looks like they are doing a port switching in transit from 443 to 63658 most proxies and firewalls will kill this connection. Make sure the *.cryptlex.com is also allowed on port 63658 as well. You could probably get away with api.cryptlex.com as long as your proxy allows port connects on 63658 which by default they would not.

[JeffS (Jeffrey Schaper)]

Thanks Corey, that’s fixed our issue