DirectAdmin 1.683

[fln]

We are happy to announce the release of DirectAdmin 1.683.

A full release change log is here:

DirectAdmin 1.683
​

The update should be automatically available for all installations subscribed to the current release channel.

We appreciate all the feedback on forums and issues reported in the ticketing system.

Thanks!

 

[CAISC]

In changelog under Software update i see -

• csf updated from 14.24 to 15.00
  
  from what source CSF core files will be retrieved now.

 

[romans]

In changelog under Software update i see -

• csf updated from 14.24 to 15.00
  
  from what source CSF core files will be retrieved now.

It comes from here: https://files.directadmin.com/services/csf-15.00.tar.gz

 

[fln]

from what source CSF core files will be retrieved now.

The latest CSF 15.00 release is published in the official Way to the Web repository. We store a copy of the latest package on our mirror servers be able to add version number to the filename. And to open a path for releasing new versions in the future.

 

[eva2000]

The latest CSF 15.00 release is published in the official Way to the Web repository. We store a copy of the latest package on our mirror servers be able to add version number to the filename. And to open a path for releasing new versions in the future.

How would DA 1.682+ or the routines for v15.00 GPLv3 switch impact things if I decide to switch to my own hosted CSF mirror version that restores the download/version check routines in CSF - so that CSF -u and auto updates will look to my CSF mirror for updates? My mirrored CSF version with restored version check/download is currently on v15.01 version label. Just curious if DA 1.682+ would overwrite my mirrored CSF v15.01 version?

 

[Ohm J]

@eva2000

From my test, It's just same logics as CSF it self doing, download the source, extract, and execute "install.sh" to update.
So your customize source code might be rewritten

If you have many customize the source code outside "/etc/csf/" , just disabled it from custombuild.

 

[eva2000]

@eva2000

From my test, It's just same logics as CSF it self doing, download the source, extract, and execute "install.sh" to update.
So your customize source code might be rewritten

If you have many customize the source code outside "/etc/csf/" , just disabled it from custombuild.

Looks like it's already disabled?

cat /usr/local/directadmin/custombuild/options.conf | grep -i csf
csf=no

./build
Install/update server components
--------------------------------
  da build awstats                                   # disabled by options.conf
  da build csf                                       # disabled by options.conf
  da build dovecot_fts_xapian                        # disabled by options.conf

So installed my CSF v15.01 version

csf -v
csf: v15.01 (DirectAdmin)

csf -u
csf is already at the latest version: v15.01

 

[Richard G]

cat /usr/local/directadmin/custombuild/options.conf | grep -i csf

Don't know, I just updated da and did a version update and it's still yes. However, I did upgrade to 15 before the DA update, don't know if that makes any difference.

 

[kristian]

Looks like this update somehow broke the ModSecurity interface. Advanced Features -> ModSecurity shows this message:

 

[DrWizzle]

Looks like this update somehow broke the ModSecurity interface. Advanced Features -> ModSecurity shows this message:

I'm running Ubuntu 24.04 and updated to 1.683 last night, Mod security is ok here for me on admin and user panels?

 

[exlhost]

Don't know, I just updated da and did a version update and it's still yes. However, I did upgrade to 15 before the DA update, don't know if that makes any difference.

Same over here. But updated after DA update.

 

[kristian]

I'm running Ubuntu 24.04 and updated to 1.683 last night, Mod security is ok here for me on admin and user panels?

Hm, you're right. It seems to be working for some accounts, but not for others, on the same server. I got three reports in a row, so I assumed it was a general issue. I tried to remove the modsec_audit.log which did not help. There is no indication of any error in any logs, and I didn't see anything special while running directadmin in debug mode. It happens on servers both with Apache and Litespeed.

 

[kristian]

Hm, you're right. It seems to be working for some accounts, but not for others, on the same server. I got three reports in a row, so I assumed it was a general issue.

It does seem like a general issue actually, and it is related to 1.683, but it's not affecting all users.

On one of our servers where this happens, I tried to downgrade DA to 1.682 a96573edc6aa43ea1753ca4694779a3ac5254598, and the error went away, ModSecurity loaded like usual. When I upgraded back to 1.683 c74812386392d0540785cf432941ae820fb0ad1b the error appeared again.

Edit/update: It seems the error only happens for the "main domain" on an account, if the account has multiple domains.

 

[infracom2005]

any update of this??

since version 1.682 the date of overwritten files is not updated in File Manager, but the correct date appears in FTP.

i attah capture of file manager and ftp, same folder, same files but filemanager doesn´t update the date after overwrite file

 

[Ohm J]

@infracom2005
It's showing the date created. you need to click that date and it will show the updated date.

 

[romans]

Looks like this update somehow broke the ModSecurity interface. Advanced Features -> ModSecurity shows this message:

We aware that issue and developers are notified. It happens only for domains which have subdomains created ... HotFix will be released ASAP.

 

[fln]

Thanks for reporting the issue @kristian. A new build is released with fixes to modsecurity page and user info page.

 

[kristian]

Thanks for reporting the issue @kristian. A new build is released with fixes to modsecurity page and user info page.

Great! Can confirm that 1.683 0a93d390d286c658b5db29a10bf650e72e00bb1e fixed it.

 

[sysdev]

If I look in the controlpanel (custombuild) I don't see any updates (legacy and new), but if i run 'da build versions' I do see updates (that also can be installed with 'da build update_versions'.

 

[romans]

If I look in the controlpanel (custombuild) I don't see any updates (legacy and new), but if i run 'da build versions' I do see updates (that also can be installed with 'da build update_versions'.

I recommend creating a ticket and provide SSH access to your DA server to check the situation closer to understand the reason of that issue there.