There is no ionCube loader available for PHP 8.1.

Support has been added to the latest version of CB.
Hello smtalk, I have CB 2.0.0 (rev: 2902)
:
  • Executing /usr/local/directadmin/plugins/custombuild/admin/build ioncube...
  • Downloading ioncube_loaders_lin_x86-64.tar.gz...
  • #=#=# ##O#- # ##O=# # 0.1% 0.4% 0.7% # 1.6% ## 3.1% #### 6.4% ######### 12.8% ################## 25.4% ################################## 48.1% ################################################### 70.9% ################################################################### 93.3% ######################################################################## 100.0%
  • There is no ionCube loader available for PHP 8.1.
  • ionCube loader 11.0.1 is now installed for PHP 7.2.
  • Restarting php-fpm81.
  • Restarting php-fpm72.

  • Done!
 
[root@vhost custombuild]# ./build update
########################################################################################### 100.0%
Extracting custombuild.tar.gz...
Cronjob is set for [email protected]:
Cronjob frequency: weekly
Automatic notifications: yes
Automatic updates: no
Installing sa-update cronjob...
Downloading sa-update.sh...
########################################################################################### 100.0%
Automatic SpamAssassin rule updates: daily
[root@vhost custombuild]#

but I see that it has not been updated to (rev: 2929), why?
 
[root@vhost custombuild]# ./build update
########################################################################################### 100.0%
Extracting custombuild.tar.gz...
Cronjob is set for [email protected]:
Cronjob frequency: weekly
Automatic notifications: yes
Automatic updates: no
Installing sa-update cronjob...
Downloading sa-update.sh...
########################################################################################### 100.0%
Automatic SpamAssassin rule updates: daily
[root@vhost custombuild]#

but I see that it has not been updated to (rev: 2929), why?
Try:
Code:
wget -O /usr/local/directadmin/custombuild/build http://files1.directadmin.com/services/custombuild/2.0/custombuild/build
/usr/local/directadmin/custombuild/build update
 
custombuild]# php -i |grep ionCube
with the ionCube PHP Loader v12.0.1, Copyright (c) 2002-2022, by ionCube Ltd.
ionCube Loader


and EN-ClamAV : Site error: the ionCube PHP Loader needs to be installed. This is a widely used PHP extension for running ionCube protected PHP code, website security and malware blocking. Please visit get-loader.ioncube.com for install assistance. :LOL::LOL:

why ? I build ioncube , restart httpd, restart directadmin , same error,
 
[root@vhost custombuild]# php -v
PHP 8.1.9 (cli) (built: Aug 15 2022 16:18:29) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.1.9, Copyright (c) Zend Technologies
with the ionCube PHP Loader v12.0.1, Copyright (c) 2002-2022, by ionCube Ltd.

I get the same error on softaculous ,, ( Site error: the ionCube PHP Loader needs to be installed. This is a widely used PHP extension for running ionCube protected PHP code, website security and malware blocking. Please visit get-loader.ioncube.com for install assistance. _
 
Don't use defaul php (php1_release=8.1)
wait until clamav and softaclouds and others supporting php 8.1 whit ioncube v12

use php1_release=7.4 and use from one of them php2_relase= php3_relase= php4_relase= php 8.1

rebuild your php again with php1_release=7.4 then clamav and softaculous will works again.
 
Don't use defaul php (php1_release=8.1)
wait until clamav and softaclouds and others supporting php 8.1 whit ioncube v12

use php1_release=7.4 and use from one of them php2_relase= php3_relase= php4_relase= php 8.1

rebuild your php again with php1_release=7.4 then clamav and softaculous will works again.

Agreed.

For now, we're deploying with PHP 7.4 out-the-box to maintain compatibility with Softaculous.

I just tried Softaculous again a few minutes ago, but it failed:

Code:
# sh install.sh
Last metadata expiration check: 0:00:40 ago on Mon Aug 15 15:48:48 2022.
Dependencies resolved.
Nothing to do.
Complete!
-----------------------------------------------
 Welcome to Softaculous Apps Installer
-----------------------------------------------

///////////////////////////////
// INSTALLING SOFTACULOUS
// Detected Panel : Directadmin
// Softaculous Package already exists, Skipping Download...
// Use --force-download parameter to forcefully download the package
PHP Fatal error:  The file /usr/local/directadmin/plugins/softaculous/includes71/main/functions.php encoded as type [1/71] cannot be decoded by this version of the ionCube Loader.
 in Unknown on line 0
 
Try:
Code:
wget -O /usr/local/directadmin/custombuild/build http://files1.directadmin.com/services/custombuild/2.0/custombuild/build
/usr/local/directadmin/custombuild/build update
I did that and got "File not found" and on top of that the build file is now 0 bytes so now totally screwed.
 
You should follow the official guide and update DirectAdmin, custombuild is now part of DirectAdmin, that's not how it's updated or distributed anymore...

So how do I fix it now?

I am a little frustrated with the way things are going now. I understand things change but the post I followed is less than a year old and when I followed it, it made things worse and zeroed out the build file. There doesn't seem to be any effort to remove old posts that not only do not work but can actually cause damage to the system.
 
Do the update and it will update DA and custombuild, it's no longer separate, and there are release channels. There's also only one mirror address, it's a CDN now. It's a good idea to check the documentation and release information once in a while. Quite a bit of things have changed in the last 6 months. I would not expect anyone to delete forum posts as things change, that's not a normal practice, that's what the documentation is for, it's updated as things change.

 
da update didn't fix it. I had to do the manual update.

I don't expect forum posts to be deleted but I also don't expect the commands from a developer to do damage to my system. I don't know the answer. I was not happy when I was trying to fix one problem and then I had to stop and fix another that was caused by a supposed solution.

The real answer to the ioncube php 8.1 problem is to edit the file php_extensions.conf.
 
The real answer to the ioncube php 8.1 problem is to edit the file php_extensions.conf.
What do you mean, to install ioncube? You don't need to edit that file.

This is the method to install (for a longer time already)
Code:
cd /usr/local/directadmin/custombuild
./build update
./build set_php "ioncube" yes
./build "php_ioncube"
 
What do you mean, to install ioncube? You don't need to edit that file.

This is the method to install (for a longer time already)
Code:
cd /usr/local/directadmin/custombuild
./build update
./build set_php "ioncube" yes
./build "php_ioncube"
According to this thread less than 9 months ago its "./build set ioncube yes" and it was never corrected. My complaint is that significant changes were made and no corrections have been made.

So when running "./build set ioncube yes" instead of coming back with the error "ioncube is not a valid option" how about stating "The new command is "./build set_php "ioncube" yes"

A perfect example is the build command for ioncube. The old command was "./build ioncube" and that still works. It's the exact same output as "./build php_ioncube." Why can't "./build set ioncube yes" do the same as "./build set_php "ioncube" yes"?

I love DirectAdmin and will always promote it.
 
My complaint is that significant changes were made and no corrections have been made.
Yes but as already said you can't expect threads to be change, there are too many threads around with info which should be changed then in threads, that is undoable.

The docs are up to date and that is the first place to start or doublecheck, the correct commands were present in the docs.

But you are correct, the command was ./build set ioncube yes before.
I also don't know as to why this was changed to ./build set_php "extension" yes later on.

Maybe it's announced in one of release changelogs, I don't know.
 
I also don't expect the commands from a developer to do damage to my system

That's why it is a bad practice to copy-paste commands on live systems without testing them in a sandbox environment. Directadmin used to have mirrors (and they hosted custombuild scripts and other source files) and some of them potentially could be infected, and no one would guarantee that a file or script downloaded from there is harmless. So it's an admin's responsibility to check commands and files they download.

p.s. Jeff always told he does not guarantee anything you do using his commands, but can guarantee his work to be done perfect. I like his approach. He was great. I would like to see the same warnings and notices from other posters, but who would read them?
 
I would like to see the same warnings and notices from other posters, but who would read them?
That's a good tip. At least I will try to think about this.
However, still... commands which worked half a year ago on the forums and were correct, can just change due to an update, like this extension installation command.
So in fact the "use at your own risk" is always applyable when using the forums imho.
I miss Jeff too indeed. :cry:
 
Back
Top