DirectAdmin 1.707

Hello,

A stable release is still 1.705? Not 1.706?

Bash: 
# dig +short -t txt stable-version.directadmin.com
"v=1.705&commit=610f28d2f77c98e008717f99284d2919229a5f12&rt=2026-07-23T14:29:00Z&du=120h&df=12h"
 
Yes. The stable release channel is still 1.705. We are still considering if we should cherry-pick some changes from 1.707 into 1.706 before pushing it to stable, or keep stable locked to 1.705 for one more release.
 
That's good. I believe the stable version should be updated much less frequently than it is now, especially with things that are breaking changes in some environments. Alternatively, something like an LTS should be created.
 
Last edited:
A new build is released with two changes:
  • The MX records page was not visible for users with blocked dnscontrol in user.conf. It will be visible now.
  • Webserver configuration logic that selects which certificate to use has a legacy fallback to use the main domain name certificate even if certificate does not cover the main domain name. It can be useful for non-standard configurations when main domain website is not served by DA server.
 
We've been waiting for the new stable release so we can update nginx to 1.31.3. It was released on july 15 and I believe we still cannot update it for DA unless we use the mainline release?

I was happy to hear a new version has been released but now it seems we still cannot install the nginx security update?

What's the most sane way for this? Should we run mainline if we want quick security fixes?
 
nielsh said:
We've been waiting for the new stable release so we can update nginx to 1.31.3. It was released on july 15 and I believe we still cannot update it for DA unless we use the mainline release?

I was happy to hear a new version has been released but now it seems we still cannot install the nginx security update?

What's the most sane way for this? Should we run mainline if we want quick security fixes?
Click to expand...

change version manually in Custom Build > Versions ? I never tested it with Ngjnx but I change versions on the LiteSpeed Enterprise server as build 0 which came with previous release have issues with cleaning cache so manually switched to build 1 as recommendation from LS Support before DA pushed the current one with build 6 ...

===============

Any way I'm here to ask something else

@fln - cpanel released security update for theri csf fork https://support.cpanel.net/hc/en-us/articles/42503837957015-Security-CSF-Security-Release ( I notice we too have CSF update) are we affected / patched ?
 
@DanielP, the default DA installation is not affected. There is a vulnerability in the CSF captcha/messenger feature. Users who manually enabled it are effected. We are planing to release new CSF build with captcha/messenger feature completely removed.
 
You must log in or register to reply here.
Back
Top