ionCube error: the file cannot be decoded by this version of the Loader
cannot be decoded by this version of the ionCube LoaderShort answer
The plugin's files were encoded for a newer ionCube Loader than the one PHP has loaded, or no Loader is loaded for the PHP version your site runs. Install the current Loader for that exact PHP version with the ionCube Loader Wizard, restart PHP, and reload the site. Ask the plugin vendor if the file still fails.
Fix it fast
1Find out which cause you have
Find out which PHP version serves the site. The Loader must be built for that exact version. Check the web PHP, not only the command line, since they can differ.
php -v2Match what you see, then jump to its fix
- 1
The plugin or theme was just installed or updated, and the Loader on the server is older than beforeThe installed Loader is older than the one the files needFix - 2
The Loader is set up in php.ini but the Loader Wizard still reports it as not loadedThe Loader file does not match the PHP version, thread safety or architectureFix
- 1
What does the error look like?
cannot be decoded by this version of the ionCube Loader
Cause 1 of 2
The installed Loader is older than the one the files need
1Check
ionCube Loaders run files from earlier Encoder versions, but not the other way round: a new file can need a new Loader. Encoders can also set a Minimum Loader version that stops files running on a Loader older than that number.
php -v2Fix
Install the latest Loader for your PHP version. The ionCube Loader Wizard is the recommended route: it inspects the server and tells you which Loader file to use and what to change in php.ini.
# upload the Wizard from ioncube.com/loaders.php to your web space,
# open it in a browser and follow its instructions, then
sudo systemctl restart php8.3-fpm3Verify
Open the Loader Wizard again, then reload a page that uses the plugin.
sudo systemctl restart php8.3-fpmConfirmed by ioncube.com
Cause 2 of 2
The Loader file does not match the PHP version, thread safety or architecture
1Check
ionCube ships separate packages by operating system, 32 or 64 bit, and for Windows by Visual C++ build and thread-safe or non-thread-safe. A file built for another PHP version will not load.
php -i | grep -i -E 'Thread Safety|Architecture|Loaded Configuration File'2Fix
Download the package that matches those values, point zend_extension at it, and restart PHP. If you do not know the values, ask the hosting company or use the Wizard.
; php.ini: use the zend_extension line the Loader Wizard shows
; for your server, then restart PHP3Verify
Restart PHP, then open the Loader Wizard in the browser again: it should report the Loader as installed.
sudo systemctl restart php8.3-fpmConfirmed by ioncube.com
How do I stop it coming back?
- Update the ionCube Loader whenever you change the PHP version, since each PHP version has its own Loader file.
- Read the plugin's requirements page for the Loader version it expects before upgrading it.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
Related fixes
Back end
Android gets HTML instead of JSON from a PHP API
org.json.JSONException: Value <br of type java.lang.String cannot be converted to JSONObject
The response body is not JSON.
2 causes, each with a fixBack end
Apache returns 403 when a URL contains %3F
a request like /page%3Fname=test is refused while /page?name=test works
Recent Apache httpd blocks a rewrite when the request contains an encoded question mark (%3F) and the rewritten target has a literal ?.
2 causes, each with a fixBack end
Apache returns 500 with Premature end of script headers
500 Internal Server Error
Apache ran your script, but the script printed no valid HTTP header before its output.
3 causes, each with a fixBack end
Apache returns 503 or 504 because PHP-FPM did not answer in time
Error dispatching request
Apache sent the request to PHP-FPM and gave up waiting.
3 causes, each with a fixBack end
AWS SDK for PHP cannot get credentials from the instance profile metadata server
Error retrieving credentials from the instance profile metadata server.
The SDK tries the EC2 instance metadata service when it has no valid credentials from anywhere earlier in its chain.
4 causes, each with a fixBack end
AWS SDK for PHP rejects requests: the signature is from the future
Signature not yet current: {date} is still later than {date}
AWS compares the timestamp in your signed request with its own clock.
2 causes, each with a fix