Search results

@patrickkasie in DA 1.657 nothing was changes regarding this (except DA now detects a couple more old libraries). Removing old libraries from /usr/local and rebuilding software components should solve the issue. If it does not - please open a support ticket.

Thanks for reporting, a simple workaround would be to download the files manually (from our files server) and place them in CB cache directory: curl -o /usr/local/directadmin/custombuild/cache/MariaDB-client-10.3.39-1.el8.x86_64.rpm...

To solve this issue permanently please issue the following commands as root: da config-set autoupdate 1 da config-set autopatch 1 da update This will make sure you are running latest DirectAdmin version and ensure you will receive the updates automatically.

@davidc you can still have up to 4 PHP versions configured in CustomBuild and installed on the system. The second version mentioned in the change-log is referring to the feature where two PHP version handlers can be configured on the webserver for a single domain (.php files executed with first...

If the same website works with PHP 7.4 on RHEL 8 system, but does not work on RHEL 9 please fill an issue and we will investigate this further.

@gate2vn could you please clarify what bug do you have in mind?

This version is already available in current release channel. Release channel stable is usually one version behind current. So 1.657 will be available in stable once 1.658 is released to current.

Custom configure scripts are highlighted in the CustomBuild GUI. Example: I am not sure if printing some text in CB output would help. It requires users paying much more attention to the output, and CB output is already quite verbose so it is easy to miss it.

Hi everyone! We are happy to announce the release of DirectAdmin 1.657. Focus of this release was improved PHP compatibility making old PHP versions compatible with modern systems and adding PHP 8.3 support. Full release change log can be found here: DirectAdmin 1.657 The update should be...

Hi everyone! We are happy to announce the release of DirectAdmin 1.657 RC. Focus of this release was improved PHP compatibility making old PHP versions compatible with modern systems and adding PHP 8.3 support. Full release change log can be found here: DirectAdmin 1.657 The update should be...

Exim itself is fine with old and new message IDs, so migrating them to new format is entirely optional. For external systems exim_id_update -u fixes message IDs. Old message IDs can cause transient problems in DA GUI, but old format message IDs are being replaced by new ones as the time goes...

Question seems to be a bit off-topic :). DA 1.657 does allow using PHP 5.6 on Ubuntu 22 (this combination is covered by daily build test suite). Can not give any guarantees about Ubuntu 24 we will see once it is released and once we try running tests on it.

Please keep in mind that using CentOS Stream is also an option. CentOS Stream 8 and CentOS Stream 9 are fully supported by DirectAdmin.

Yes, ImageMagic is still being installed in /usr/local. It is OK to have these files they are actually being used by PHP builds created by CustomBuild. Removal of custom libnghttp2 is already added in DA 1.657 (currently in alpha).

@huseyinktk please open a support ticket regarding this issue. I have not seen errors or reports related to libkrb5.so before. If I had to guess I would say it is caused by - some old libraries still present on the system or CB customizations or non standard packages being installed on the system.

We got reports with apache failing to start if modsecurity is used and it is linked against old custom lua library in /usr/local. Next DA version 1.657 (in alpha release channel right now) already have custom lua detection and removal scripts. It will be reported as other old libraries with the...

Just removing .so files will not help, because most likely you will have headers in /usr/local/include for the removed libraries, which shadow the include files from system packages in /usr/include. Best way forward is to remove all CB customizations, then remove the old libraries using DA...

Most of the errors can be resolved by just removing all of the old libraries (including iconv with da build remove_old_local libiconv, which is not removed with the bulk da build remove_items commands) and rebuilding all the software that stopped working due to library removal. Original post by...

An update is released to fix the large icons in the login-as header (quick user switch drop-down), thanks @kristian and @JosKlever Edit: CB message typo is fixed as well, thanks @Erulezz

Removal of old libraries needs to be performed manually, because it can really depend on how much local system is customized, but here is the general guidelines how to perform old libs removal minimizing the service downtime: Run da build list_removals to get a list of legacy libraries...