PHP Selector + IonCube == Internal Server Error

[Tcalp]

Hey Guys,

I've had a ticket open with CloudLinux on this since June of this year (#HCJ-430-39668). Whenever someone attempts to use IonCube on PHP selector it causes an internal server error. I know that this library can be a bit glitchy in terms of the order it is initialized in and such, though there doesn't seem to be this level of control within CL , I have tried disabling all Zend modules just in case as I know they commonly conflict (load order).

Thus far, I haven't had any real word for resolution of the issue with the CL staff and almost all of our clients use IonCube and figured I'd reach out here to see if anyone in the community is aware of how to resolve the issue.

 

[cPanelMichael]

Hello

Could you elaborate on the most recent communication in the support ticket? For instance, is there an internal case or bug report that's addressable?

Thank you.

 

[Tcalp]

Hey Michael,

I actually had gotten in touch with IonCube support and we updated the IonCube loader from 5.0.10 to 5.0.18 (released Sept 14), it and resolved the memory crash in the IonCube loader that was causing the internal server error. I passed the info/resoution onto the team and CL and they'll be pushing the new loaders into the repo next Monday.

 

[cPanelMichael]

I am happy to see the issue is addressed. Thank you for updating us with the outcome.