ionCube Loader is not loaded. Please enable it to continue installation
-
problem fixed..thank you 0 -
Hey there! Can you share what the solution was so we can all learn together? 0 -
/////////////////////////////// // INSTALLING SOFTACULOUS // Detected Panel : cPanel // DOWNLOADING SOFTACULOUS PACKAGE Could not download the Softaculous Package!Softaculous did not installed. Have you enabled Ioncube loader ? Please check : Page Not Found 0 -
NOW i am facing this issue!! 0 -
Log into WHM. Choose Tweak Settings. Search for "cPanel PHP Loader". Make sure that ioncube is checked. Save. 0 -
Log into WHM. Choose Tweak Settings. Search for "cPanel PHP Loader". Make sure that ioncube is checked. Save.
thanks for your response! already i checked! still not working. same issue! softaculous reinstall will help?0 -
What version of PHP is set to the default on the machine? 0 -
What version of PHP is set to the default on the machine?
i have reinstalled all,, and now it's fixed. it was a new fresh server.0 -
Can I get some docs on troubleshooting ionCube for Softaculous?
It is enabled in Tweak settings, but Softaculous won't load, reporting ionCube is not installed ("Script error: the ionCube Loader for PHP needs to be installed.").
It was working yesterday, but won't load today.
(AlmaLinux v8.10.0 cPanel v120.0.12)
0 -
Dear all,
We are facing the same issue here after version 120.0.12, PHP 7.4, 8.1, and 8.2.
0 -
Softaculous uses the cPanel system PHP (which was updated to 8.3). And cPanel knew from previous reports that this was going to happen when people updated to WHM 120.0.12 and the system PHP was updated to PHP 8.3.
For the life of me I don't know how they allowed WHM 120.0.12 to be pushed to the next tier given that they knew this would happen.
https://www.softaculous.com/blog/softaculous-not-working-on-cpanel-v120-0-12/
2 -
Thank you mtindor!
TL;DR the workaround is to run on an affected server
wget -O /usr/local/cpanel/3rdparty/php/unversioned/ioncube/ioncube_loader_lin_8.3.so https://files.virtualizor.com/ioncube/64/ioncube_loader_lin_8.3.so
cPRex If mtindor's information is correct (seems to be), I have questions:
1- Seriously, WHAT ON EARTH IS WRONG with your dev team?! (Don't lose your job over it, but give us the honest answer.)
2- As widespread as Softaculous is inside the cPanel community, they KNEW the problems this would cause. What is the logical reason for doing this?!
3- The information was there at LEAST six days ago! Why not send out a notice with the workaround AHEAD of time, or put that information in WHM as a notice? (Clearly cPanel knows how to do that when you want up-sell us... *eye roll*)
4- WHY would they drop ionCube anyway?
5- When will the one month refund to all affected licenses be issued? (I'm 100% serious! Show us you are professionals and understand proper business procedures. This is surely causing huge amounts of tech time dealing with end users, not to mention the hit our reputations take - this is all on you, cPanel.)
Signed, I-shouldn't-even-have-to-be-writing-this
0 -
Softaculous v6.0.8 release notes:
1) [Task] In cPanel v120.0.12, ionCube loader is not loaded in 3rd party PHP binary causing Softaculous to fail. Softaculous will now add the ionCube loader in case cPanel does not add it.
0 -
This is getting annoying. Every time cPanel releases something, it comes with problems, it feels like an endless beta. Doesn't WHMCS and others use ionCube in their applications?
How can a person or team approve such an incomplete release?
Now, SitePad, Softaculous, cPGuard, and others are all broken because of this unplanned update. We've been dealing with this lack of professionalism on our side for days.
0 -
DELTA SERVERS iNC The work-around above fixes Softaculous. Does it get all those working for you?
Agreed, though, that we shouldn't need to be dealing with this at all.
0 -
Yes for Softaculous, SitePad has updated the application to work around this, cPguard as well, and we are waiting for others.
It is unfortunate that something expensive is causing this.
The trust in updating cPanel is negative; it is worse than keeping it as it is.
0 -
Hey there! I did want to say this is resolved in the latest builds, 120.0.14 and 122.0.2, so you shouldn't need to perform additional manual workarounds at this point.
0
Please sign in to leave a comment.
Comments
17 comments