Skip to navigation

Fix connection and sign-in errors

Start with the returned code

AuthlyX returns a stable code and a readable message. Developers can customize many server messages, so application logic should check the code or success result rather than compare English sentences.

No Yes Request fails Did a verified server reply arrive? Check network, endpoint and trusted keys Read the returned code Correct credentials, accesspolicy or identity status Use valid offline access only ifalready permitted

Invalid AppKey

Copy the AppKey from the same application as the license or user. Remove accidental spaces and check that the SDK points to the intended local or production API. An old owner ID or app secret is not a V3 AppKey. Rotating the key does not automatically update installed software.

Device limit reached

Open the identity’s linked devices. Confirm the configured device limit and remove a device only when the developer’s replacement policy permits it. Repeatedly generating a new installation key is not a valid workaround: it can trigger an installation-key-change rejection.

Session ended, expired or revoked

Ask the customer to sign in again after resolving the underlying status. If the identity is banned, paused or expired, simply repeating initialization will not restore access. Stop protected requests when the server definitively rejects the session.

Signature failure

Confirm the SDK trusts the correct public verification key for this API. Proxies must not modify signed response data. Direct clients must sign the exact request bytes, method and path with a fresh nonce and server-aligned timestamp. Never disable signature verification to make an error disappear.

Country blocked or reputation lookup unavailable

Review the application’s Access Policies. A blocked-country decision and an unavailable VPN lookup are different failures. Check trusted proxy settings before changing the customer’s access rules.

Update required

Compare the customer’s version with Allowed Versions and the assigned release channel. A download URL in a release does not automatically make that version allowed to connect.

Protected storage unavailable

Check that the application runs under a normal supported user profile and can access its configured protected store. Do not replace the store with plaintext or silently create a new installation identity. Preserve the error and let the customer resolve the environment issue.

When reporting a problem, include the SDK/runtime version, API hostname, returned code and request ID. Remove passwords, tokens and full license keys from the report.