Error reference

Find common RelyAI messages grouped by category below. Each entry explains the cause and resolution. For step-by-step diagnostic workflows, see Troubleshooting.

ionCube

RelyAI requires ionCube Loader to run its encoded files:

Requirement: ionCube Loader 13.0.2 or newer matching your PHP version.
Symptom: RelyAI fails to load or shows a fatal encoding error.
Fix: Install or enable the loader in your PHP configuration, restart your web server, and reload. See Requirements.

License and access

Message	Meaning and fix
"Enter a valid RelyAI license key to enable AI features."	No key is registered yet. Add and Activate your key under RelyAI → Settings → License.
"Your RelyAI license could not be verified. Please check your key."	The key failed verification. Confirm the key, then Re-activate on the License tab.
"RelyAI is not licensed on this install. Ask an administrator to activate a license key."	An AI request ran while unlicensed. An admin must activate a valid key for this domain.
"License could not be activated: :reason"	Activation was rejected; the reason is shown. Fix the stated cause (domain, IP, or install path) and try again.
"License deactivated on this domain."	Confirms the key was released from this domain. Re-activate here or on another domain to restore AI.

Engine and API key

Message	Meaning and fix
"No AI API key is configured. Please set one in Admin → RelyAI → Settings."	No engine key is set. Add an engine and key under RelyAI → Settings → Engines & Keys.
"Connection successful"	The Test Connection check passed — your engine and key work.

See Connect an engine.

Updates

Message	Meaning and fix
"Could not reach the update server (…). Your plugin continues to work normally."	The updater couldn't reach the server — often just because no release is published yet. AI keeps working; try again later.
"Your Support & Updates plan has expired or is not active…"	Installing new releases is blocked for this key. Renew Support & Updates; the installed version keeps working.
"v:v is published but its download is not yet available — please contact support."	A release exists but its download isn't ready. Contact support.
"Update failed: :reason"	The update didn't apply; the current version is auto-restored. Check the reason and retry, or update manually.
Verification failed during an update	The downloaded build failed its integrity check and was not applied. Retry, or update manually via Admin → Plugins → Upload Plugin.