DirectAdmin 1.709

[fln]

We are happy to announce the release of DirectAdmin 1.709.

A full release change log is here:

DirectAdmin 1.709​

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!

 

[stefantriep]

I see 1.709 twice in the list in the documents, one with the link of 1.710

 

[fln]

Thanks @stefantriep. The empty docs page was a placeholder for the next DA 1.710 release with an incorrect title. The title is fixed now.

 

[Remco00]

Stable channel still on 1.705. Correct?

 

[exlhost]

After this update, SSL is no longer working correctly for subdomains. I’m getting HSTS errors, regardless of whether I use a wildcard SSL certificate, a regular certificate, or ZeroSSL.
It even requested a new SSL which was not needed.

Every update seems to introduce new SSL-related problems.

 

[fln]

@exlhost, could you please share some details or open the support ticket. This is not something we see on our test servers.

 

[Can]

@fln After updating to DirectAdmin 1.709, the Brute Force Monitor (evo/brute-force-monitor) is no longer working correctly on my server.

The issue is not limited to the monitor itself — the Brute Force Monitor link does not open/work when clicked, and I cannot access the page through the Evo interface.

This started immediately after the DirectAdmin 1.709 update.

Could you please check whether there is a problem with the Evo Brute Force Monitor route/page in 1.709 and advise how this can be fixed?

DirectAdmin version: 1.709
Affected area: evo/brute-force-monitor
Problem: Link/page does not open or function after the update.

 

[fln]

@Can, the BFM page work as expected on our test servers and on the demo.directadmin.com.

Maybe it is something specific to your server. Please open a support ticket and we will investigate it further.

 

[exlhost]

@exlhost, could you please share some details or open the support ticket. This is not something we see on our test servers.

We did that, I followed Roman's steps, you can read my response there. Please note that when we have performed the update from 1.708 to 1.709 again, we will see on the SSL page from the current the SSL certificate: New certificates are waiting to be provisioned.