Troubleshooting

The Loader doesn’t show up after installing

If php -m doesn’t list oxrion, or phpinfo doesn’t show the Oxrion Loader:

• Restart your web server or PHP service (e.g. PHP-FPM) after editing php.ini — changes don’t apply until you do.
• Check the extension= line points to the correct file name.
• Confirm the file is in your PHP extension directory (extension_dir).
• Make sure the build matches your PHP version and platform — see Choosing the right build.

A protected file won’t run

If the Loader is installed but a specific file won’t run:

• It’s a private file and the external key is missing. Private files need the external key on the server. See External keys.
• The license doesn’t match. If the file is licensed, confirm the .lic is present, the domain matches the server, and the license hasn’t expired. See Protecting your code.
• The file was modified. Protected files are tamper-proof; if a byte changed (e.g. during a bad upload or text-mode transfer), the Loader rejects it. Re-download or re-deploy the original protected file.

A wrong-version or thread-safety error appears

PHP failing to load the extension is almost always a build mismatch. Re-check php -v (and on Windows, thread safety) against the file you installed. See Choosing the right build.

A file stopped running after 90 days

That’s the Free plan behavior — files run for 90 days and carry a trial notice. For files that run indefinitely with no trial marking, use Pro. See Plans & limits.

I can’t recover a file

Recovery only works if the file was encoded with Recovery Mode enabled and you have the matching private key. Without both, the file can’t be restored to source. See Recovery.