DirectAdmin 1.668

This is the last release supported by RHEL 7 and Debian 10 systems. Some users were confused why they do not get new DA releases.

We just pushed out an update to EOL systems to show the distro EOL status in the DA version page.

1731685038896.png
 
Maybe it's a good idea to also give such clear notice to users when installing directadmin, that they have to wait until background installation is finished before doing any user and domain configuration.
Some don't know and this often leads to odd issues as we encountered on the forums.
There is a notice that background stuff is still busy and a message will come when ready, but it's not clear they can better wait configuring until it's ready.
 
EOL release channel for RHEL 7 and Debian 10 systems got a new patch release. It bumps the versions of CB managed software components:
  • apache2.4 updated from 2.4.62 to 2.4.63
  • apr updated from 1.7.5 to 1.7.6
  • exim updated from 4.98.1 to 4.98.2
  • imagick updated from 3.7.0 to 3.8.0
  • ioncube_loaders updated from 13.3.1 to 14.4.0
  • litespeed updated from 6.3.1-1 to 6.3.2-4
  • MySQL 8.0 updated from 8.0.39 to 8.0.42
  • MySQL 8.4 updated from 8.4.2 to 8.4.5
  • openlitespeed updated from 1.8.1 to 1.8.3.1
  • phalcon5 updated from 5.8.0 to 5.9.3
  • PHP 8.1 updated from 8.1.30 to 8.1.32
  • PHP 8.2 updated from 8.2.24 to 8.2.28
  • PHP 8.3 updated from 8.3.12 to 8.3.21
  • phpmyadmin updated from 5.2.1 to 5.2.2
  • php_yaml updated from 2.2.3 to 2.2.4
  • roundcubemail updated from 1.6.9 to 1.6.10
 
An update is released with a RoundCube version update from 1.6.10 to 1.6.11. Roundcube 1.6.11 fixes a security issue.
 
New build ir released for RHEL 7 and Debian 10 systems. It bumps litespeed from 6.3.2-4 to 6.3.4-1 to get fix for

blog.litespeedtech.com

LiteSpeed Security Update ⋆ LiteSpeed Blog

LiteSpeed Security Update: We have fixed a vulnerability in LSQUIC that impacts all LiteSpeed Server Products. Please update now.
blog.litespeedtech.com blog.litespeedtech.com
 
On September 26, I noticed that a new DirectAdmin build was released (bca79c43d780533cba222b06b8210ccc3357cf70).
I couldn’t find any release notes about this update, but the only change I noticed is that CSF is now managed through CustomBuild, and version 15.02 has been released.

Here’s what I’m seeing:
  • On one of our servers (installed in 2023, where CSF came pre-installed), the CSF update appeared and everything upgraded correctly.
  • However, on two older servers (installed around 2020, when CSF wasn’t bundled by default), the new DirectAdmin build does not show any CSF update in CustomBuild, even after the upgrade.
Has anyone else experienced this or found a solution to enable the CSF update on older installations?
 
paulonichio said:
Has anyone else experienced this or found a solution to enable the CSF update on older installations?
Click to expand...
Yep , in that time it was installed as plugin, one of our server have that.
For now csf updates and crons are removed from that server, dont dare to remove it and use the custombuild version afraid to loose my setting there :)
 
Active8 said:
For now csf updates and crons are removed from that server, dont dare to remove it and use the custombuild version afraid to loose my setting there :)
Click to expand...
No need to be scared. Just backup your csf.conf, csf.allow, csf.ignore and csf.pignore and if you changed something then also backup the custom.regexp.pm and maybe csf.blocklist
The install via custombuild, normally things should not be overwritten, just doublecheck and if something changed (like the block smtp 0 to 1) just copy back all the backups and restart csf and lfd and things are the same again.
 
Richard G said:
No need to be scared. Just backup your csf.conf, csf.allow, csf.ignore and csf.pignore and if you changed something then also backup the custom.regexp.pm and maybe csf.blocklist
The install via custombuild, normally things should not be overwritten, just doublecheck and if something changed (like the block smtp 0 to 1) just copy back all the backups and restart csf and lfd and things are the same again.
Click to expand...

So on the servers where the automatic update to the new CSF version isn’t appearing, will I need to back up everything, uninstall it, and reinstall through CustomBuild?
Isn’t there a more automated way to do this?
 
paulonichio said:
will I need to back up everything, uninstall it, and reinstall through CustomBuild?
Click to expand...
No. Just backup and reinstall through custombuild should already be enough. If all is correct your current settings are not overwritten. But always backup to be sure.

paulonichio said:
Isn’t there a more automated way to do this?
Click to expand...
You can make a snapshot if you have a VPS. I just use SSH, make a directory /root/backup and then either use Midnight Commander or just copy the files to that directory.
 
Richard G said:
No. Just backup and reinstall through custombuild should already be enough. If all is correct your current settings are not overwritten. But always backup to be sure.


You can make a snapshot if you have a VPS. I just use SSH, make a directory /root/backup and then either use Midnight Commander or just copy the files to that directory.
Click to expand...

Thanks for the tips, @Richard G .
It seems I found the reason the update wasn’t showing in the panel.

For some reason, when I went to “CustomBuild” > “Options”, the “CSF” option was set to “No,” even though the firewall was installed and active.

I changed the setting to “Yes,” and the update immediately became available.
I then proceeded with the upgrade to version 15.02 without any problems.
 
Sir, in this 1.668 version release, we are experiencing a 500 API error.

Here are the details.
<code>
2025-09-29T17:00:55+07:00 0.003 139.99.1.3 200 218 GET /api/session/state .../evo/admin/skins sadmin|myclust session-native -
2025-09-29T17:00:15+07:00 60.004 139.99.1.3 200 94 GET /api/custombuild/state/sse .../evo/admin/skins sadmin|myclust session-native -
2025-09-29T17:01:25+07:00 0.001 139.99.1.3 200 218 GET /api/session/state .../evo/admin/skins sadmin|myclust session-native -
2025-09-29T17:01:28+07:00 0.002 178.128.0.1 500 77 POST /CMD_API_POP - myclust|myuser basic-native -
</code>
 
paulonichio said:
when I went to “CustomBuild” > “Options”, the “CSF” option was set to “No,”
Click to expand...
Be aware. Maybe you had set it to "no" afterwards, to prevent DA from changing the SMTP_BLOCK=0 to SMTP_BLOCK=1 in csf.conf when using external smtp. Seems DA sometimes changes that. However DA has to keep of that setting in the future then.
Or make an option to not change existing configs.
 
Last edited:
Active8 said:
Dont exsist it should be SMTP_BLOCK
Click to expand...
Oeps yes, I didn't bother to look but knew people would understand. It's indeed SMTP_BLOCK and it was also ON by default on normal CSF/LFD installations before DA started using it.
My mistake. I corrected my post accordingly. Thank you for pointing it out! (y)

But some people turn it to OFF to use external SMTP and I've read in some occasions then on a DA update where CSF update was set to ON in Custombuild, it was set back to ON. That should in fact not happen.
However, it's something to keep in mind if people had the CSF update set to off in Custombuild before, if they activate it again, check that this will not be changed.
 
You must log in or register to reply here.
Back
Top