Skip to content
Oxrion Docs

Verifying the loader

After installing, confirm the loader is active in the SAPI that serves your site.

The quickest check

Section titled “The quickest check”

If you installed with the CLI, one command reports whether the loader is active:

Terminal window
oxrion-loader verify

Check the extension is loaded

Section titled “Check the extension is loaded”
Terminal window
php -m | grep oxrion        # Linux / macOS
php -m | findstr oxrion     # Windows

If oxrion is listed, the extension is loaded for the CLI. Web servers (php-fpm, Apache) can use a different php.ini than the CLI — so also confirm there, and restart the web server after enabling.

Run a protected file

Section titled “Run a protected file”

The real test: deploy a protected file and load it. If it runs normally, the loader is working. If you see raw code or a blank response, the loader isn’t active for that request — see Troubleshooting.

If a file won’t run

Section titled “If a file won’t run”
  • Nothing in php -m → wrong php.ini, or the web server wasn’t restarted.
  • “signature mismatch” → the file was altered after protection, or wasn’t produced for this setup.
  • A licensed file won’t run → the license file is missing, misnamed, or bound to a different domain.

Full fixes: Troubleshooting →