NEXA_TOKEN does not work: SDKError(Invalid license)

[JoeTeglasi]

Pre-checks

• I searched existing issues
• I’m using the latest NexaSDK release

What happened?

When I try to run inference with `nexa infer NexaAI/OmniNeural-4B`, I always get `SDKError(Invalid license)`.

I expected the command to run successfully without any errors...

Steps to reproduce

Device name	Joes-Galaxy-Book4-Edge
Processor	Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) CPU (3.42 GHz)
Installed RAM	16.0 GB (15.6 GB usable)
Graphics card	Qualcomm(R) Adreno(TM) X1-85 GPU (128 MB)
Storage	224 GB of 477 GB used
Device ID	243483F7-F228-4209-8946-9FDA8377DECB
Product ID	00342-21392-65919-AAOEM
System type	64-bit operating system, ARM-based processor
Pen and touch	Touch support with 10 touch points

Edition	Windows 11 Home
Version	25H2
Installed on	‎7/‎13/‎2025
OS build	26200.8246
Experience	Windows Feature Experience Pack 1000.26100.297.0

1. Download and Install the Windows-on-ARM Nexa CLI from https://github.com/qualcomm/nexa-sdk/releases/tag/v0.2.73
[https://github.com/qualcomm/nexa-sdk/releases/download/v0.2.73/nexa-cli_windows_arm64.exe](https://github.com/qualcomm/nexa-sdk/releases/download/v0.2.73/nexa-cli_windows_arm64.exe)

2. Open Nexa CLI

3. Set `$env:NEXA_TOKEN` according to README.md. (Optional) Also set  `nexa config set license <NEXA_TOKEN>`.

4. Run `nexa infer NexaAI/OmniNeural-4B`

Logs & stack traces

PS C:\Users\joe\AppData\Local\Nexa CLI> nexa version
NexaSDK Bridge Version: v1.0.45-rc1
NexaSDK CLI Version:    v0.2.73


PS C:\Users\joe\AppData\Local\Nexa CLI> $env:NEXA_TOKEN="key/eyJhY2NvdW50Ijp7ImlkIjoiNDI1Y2JiNWQtNjk1NC00NDYxLWJiOWMtYzhlZjBiY2JlYzA2In0sInByb2R1Y3QiOnsiaWQiOiJkYjI4ZTNmYy1mMjU4LTQ4ZTctYmNkYi0wZmE4YjRkYTJhNWYifSwicG9saWN5Ijp7ImlkIjoiMmYyOWQyMjctNDVkZS00MzQ3LTg0YTItMjUwNTYwMmEzYzMyIiwiZHVyYXRpb24iOjMxMTA0MDAwMH0sInVzZXIiOnsiaWQiOiI3MGE2YzA4NS1jYjc3LTQ3YmEtOWUxNC1lNjFjYTA2ZThmZjUiLCJlbWFpbCI6ImFsYW40QG5leGE0YWkuY29tIn0sImxpY2Vuc2UiOnsiaWQiOiI4OTlhZGQ2NS1lOTI2LTQ2M2ItODllNi0xMjc0NzM3ZjA1MzYiLCJjcmVhdGVkIjoiMjAyNS0wOS0wNlQwMDo1MzozNi4yMDNaIiwiZXhwaXJ5IjoiMjAzNS0xMi0zMVQyMzo1OTo1OS4wMDBaIn19.BXoUHIEzFMuuZbBT7RvsKO9nTi5950C6kHO64blF7XBnfKvZ6ClA8a55tmszI1ZWdngzpNFTzMM5PV5euuzMCA=="

PS C:\Users\joe\AppData\Local\Nexa CLI> nexa config set license "key/eyJhY2NvdW50Ijp7ImlkIjoiNDI1Y2JiNWQtNjk1NC00NDYxLWJiOWMtYzhlZjBiY2JlYzA2In0sInByb2R1Y3QiOnsiaWQiOiJkYjI4ZTNmYy1mMjU4LTQ4ZTctYmNkYi0wZmE4YjRkYTJhNWYifSwicG9saWN5Ijp7ImlkIjoiMmYyOWQyMjctNDVkZS00MzQ3LTg0YTItMjUwNTYwMmEzYzMyIiwiZHVyYXRpb24iOjMxMTA0MDAwMH0sInVzZXIiOnsiaWQiOiI3MGE2YzA4NS1jYjc3LTQ3YmEtOWUxNC1lNjFjYTA2ZThmZjUiLCJlbWFpbCI6ImFsYW40QG5leGE0YWkuY29tIn0sImxpY2Vuc2UiOnsiaWQiOiI4OTlhZGQ2NS1lOTI2LTQ2M2ItODllNi0xMjc0NzM3ZjA1MzYiLCJjcmVhdGVkIjoiMjAyNS0wOS0wNlQwMDo1MzozNi4yMDNaIiwiZXhwaXJ5IjoiMjAzNS0xMi0zMVQyMzo1OTo1OS4wMDBaIn19.BXoUHIEzFMuuZbBT7RvsKO9nTi5950C6kHO64blF7XBnfKvZ6ClA8a55tmszI1ZWdngzpNFTzMM5PV5euuzMCA=="

PS C:\Users\joe\AppData\Local\Nexa CLI> nexa infer NexaAI/OmniNeural-4B
Sox is not installed, some features may not work. Try:
  winget install --id=ChrisBagwell.SoX -e
Then restart your terminal to make sure sox is in PATH
FFmpeg is not installed, some features may not work. Try:
  winget install --id=BtbN.FFmpeg.GPL -e
Then restart your terminal to make sure ffmpeg is in PATH
License validation failed: fail to request license host for activation
Error: SDKError(Invalid license)

Model(s) and quantization

NexaAI/OmniNeural-4B

NexaSDK version

0.2.73

Install method

https://github.com/qualcomm/nexa-sdk/releases/tag/v0.2.73

OS and version

Windows 11

Hardware / accelerator

Snapdragon X Elite

Additional context

[kenchungcwc-lab]

Same here.

[leokjau]

1. In CLI, Try this again.
   nexa config set license 'key/eyJhY2NvdW50Ijp7ImlkIjoiNDI1Y2JiNWQtNjk1NC00NDYxLWJiOWMtYzhlZjBiY2JlYzA2In0sInByb2R1Y3QiOnsiaWQiOiJkYjI4ZTNmYy1mMjU4LTQ4ZTctYmNkYi0wZmE4YjRkYTJhNWYifSwicG9saWN5Ijp7ImlkIjoiMmYyOWQyMjctNDVkZS00MzQ3LTg0YTItMjUwNTYwMmEzYzMyIiwiZHVyYXRpb24iOjMxMTA0MDAwMH0sInVzZXIiOnsiaWQiOiI3MGE2YzA4NS1jYjc3LTQ3YmEtOWUxNC1lNjFjYTA2ZThmZjUiLCJlbWFpbCI6ImFsYW40QG5leGE0YWkuY29tIn0sImxpY2Vuc2UiOnsiaWQiOiI4OTlhZGQ2NS1lOTI2LTQ2M2ItODllNi0xMjc0NzM3ZjA1MzYiLCJjcmVhdGVkIjoiMjAyNS0wOS0wNlQwMDo1MzozNi4yMDNaIiwiZXhwaXJ5IjoiMjAzNS0xMi0zMVQyMzo1OTo1OS4wMDBaIn19.BXoUHIEzFMuuZbBT7RvsKO9nTi5950C6kHO64blF7XBnfKvZ6ClA8a55tmszI1ZWdngzpNFTzMM5PV5euuzMCA=='

2. Then, to check again. key 'nexa config list' in CLI. If you find 'license: key/eyJhY2NvdW50Ijp7ImlkIjoiNDI1Y2JiNWQtNjk1NC00NDYxLWJiOWMtYzhlZjBiY2JlYzA2In0sInByb2R1Y3QiOnsiaWQiOiJkYjI4ZTNmYy1mMjU4LTQ4ZTctYmNkYi0wZmE4YjRkYTJhNWYifSwicG9saWN5Ijp7ImlkIjoiMmYyOWQyMjctNDVkZS00MzQ3LTg0YTItMjUwNTYwMmEzYzMyIiwiZHVyYXRpb24iOjMxMTA0MDAwMH0sInVzZXIiOnsiaWQiOiI3MGE2YzA4NS1jYjc3LTQ3YmEtOWUxNC1lNjFjYTA2ZThmZjUiLCJlbWFpbCI6ImFsYW40QG5leGE0YWkuY29tIn0sImxpY2Vuc2UiOnsiaWQiOiI4OTlhZGQ2NS1lOTI2LTQ2M2ItODllNi0xMjc0NzM3ZjA1MzYiLCJjcmVhdGVkIjoiMjAyNS0wOS0wNlQwMDo1MzozNi4yMDNaIiwiZXhwaXJ5IjoiMjAzNS0xMi0zMVQyMzo1OTo1OS4wMDBaIn19.BXoUHIEzFMuuZbBT7RvsKO9nTi5950C6kHO64blF7XBnfKvZ6ClA8a55tmszI1ZWdngzpNFTzMM5PV5euuzMCA=='
   ok, it works!

[JoeTeglasi]

1. In CLI, Try this again.
   nexa config set license 'key/eyJhY2NvdW50Ijp7ImlkIjoiNDI1Y2JiNWQtNjk1NC00NDYxLWJiOWMtYzhlZjBiY2JlYzA2In0sInByb2R1Y3QiOnsiaWQiOiJkYjI4ZTNmYy1mMjU4LTQ4ZTctYmNkYi0wZmE4YjRkYTJhNWYifSwicG9saWN5Ijp7ImlkIjoiMmYyOWQyMjctNDVkZS00MzQ3LTg0YTItMjUwNTYwMmEzYzMyIiwiZHVyYXRpb24iOjMxMTA0MDAwMH0sInVzZXIiOnsiaWQiOiI3MGE2YzA4NS1jYjc3LTQ3YmEtOWUxNC1lNjFjYTA2ZThmZjUiLCJlbWFpbCI6ImFsYW40QG5leGE0YWkuY29tIn0sImxpY2Vuc2UiOnsiaWQiOiI4OTlhZGQ2NS1lOTI2LTQ2M2ItODllNi0xMjc0NzM3ZjA1MzYiLCJjcmVhdGVkIjoiMjAyNS0wOS0wNlQwMDo1MzozNi4yMDNaIiwiZXhwaXJ5IjoiMjAzNS0xMi0zMVQyMzo1OTo1OS4wMDBaIn19.BXoUHIEzFMuuZbBT7RvsKO9nTi5950C6kHO64blF7XBnfKvZ6ClA8a55tmszI1ZWdngzpNFTzMM5PV5euuzMCA=='

2. Then, to check again. key 'nexa config list' in CLI. If you find 'license: key/eyJhY2NvdW50Ijp7ImlkIjoiNDI1Y2JiNWQtNjk1NC00NDYxLWJiOWMtYzhlZjBiY2JlYzA2In0sInByb2R1Y3QiOnsiaWQiOiJkYjI4ZTNmYy1mMjU4LTQ4ZTctYmNkYi0wZmE4YjRkYTJhNWYifSwicG9saWN5Ijp7ImlkIjoiMmYyOWQyMjctNDVkZS00MzQ3LTg0YTItMjUwNTYwMmEzYzMyIiwiZHVyYXRpb24iOjMxMTA0MDAwMH0sInVzZXIiOnsiaWQiOiI3MGE2YzA4NS1jYjc3LTQ3YmEtOWUxNC1lNjFjYTA2ZThmZjUiLCJlbWFpbCI6ImFsYW40QG5leGE0YWkuY29tIn0sImxpY2Vuc2UiOnsiaWQiOiI4OTlhZGQ2NS1lOTI2LTQ2M2ItODllNi0xMjc0NzM3ZjA1MzYiLCJjcmVhdGVkIjoiMjAyNS0wOS0wNlQwMDo1MzozNi4yMDNaIiwiZXhwaXJ5IjoiMjAzNS0xMi0zMVQyMzo1OTo1OS4wMDBaIn19.BXoUHIEzFMuuZbBT7RvsKO9nTi5950C6kHO64blF7XBnfKvZ6ClA8a55tmszI1ZWdngzpNFTzMM5PV5euuzMCA=='
   ok, it works!

If you check my log section, you can see that I did that...

[palazzoni]

Also the same problem....can't get valid license because now the url point to a service that is not working anymore

[leokjau]

Could it be single quotes instead of double quotes?

[palazzoni]

Debugging the process seems that the license is validated but then process try to reach http://SDK.nexa.ai that doesn't send send any response that after some time the error of license validation failed

[vitaliuwenting]

same problem in the docker container (image:nexa4ai/nexasdk:latest) on Linux with iq9

[Goribesh]

Same issue here on Snapdragon X Plus / Windows 11 ARM64 with the
identical CLI v0.2.73 + Bridge v1.0.45-rc1.

Diagnosed the root cause via packet trace — nexa-cli.exe is sending
TCP SYN to 54.200.56.5:443 (an AWS us-west-2 IP) and the host
never responds. Connection stays in SynSent state for ~21s before
the SDK times out and reports "fail to request license host for
activation".

This appears to be a decommissioned activation host. The README
explicitly states "previous token validation service has been
deprecated", but the v0.2.73 binary still hardcodes a call to it
on first NPU model use.

Confirmed:

• DNS resolves api.keygen.sh correctly
• Test-NetConnection api.keygen.sh -Port 443 succeeds
• Test-NetConnection 54.200.56.5 -Port 443 hangs / fails
• Reproduces on a completely different network (phone hotspot)
• Reproduces on every NPU model (OmniNeural-4B, phi4-mini-npu-turbo)
• log shows: "license is set by env, ignore config" — token IS read

PowerShell trace during the 21s timeout window:
PID=27192 nexa-cli -> 54.200.56.5:443 [SynSent]
(repeated for the entire timeout duration)

Additionally, pip install nexaai fails on Windows ARM64 because
the bridge zip on S3 returns 403:
https://nexa-model-hub-bucket.s3.us-west-1.amazonaws.com/public/nexasdk/v1.0.44/windows_arm64/nexasdk-bridge.zip

Both paths to NPU inference are currently broken on Windows ARM64.

[NJRBailey]

Same issue here on Snapdragon X Elite/Windows 11

[nsidhaye]

Same issue.

Interestingly not update for almost 3 months

[iwr-redmond]

#1074 (comment)

[keithem]

Yes Keith cox

…

On Sat, May 16, 2026 at 10:48 PM iwr-redmond ***@***.***> wrote: *iwr-redmond* left a comment (qualcomm/nexa-sdk#1072) <#1072 (comment)> #1074 (comment) <#1074 (comment)> — Reply to this email directly, view it on GitHub <#1072 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BN5OQIY44JJ37DEFGO4KO3343ER7PAVCNFSM6AAAAACYPFGPXOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DINRYHE4DEMJXG4> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Novatoris]

Confirming the issue. The NexaSDK Bridge binary needs to be updated.