DirectAdmin 1.661

fln

fln

Administrator
Staff member
Joined
Aug 30, 2021
Messages
1,127
Hi everyone!

We are happy to announce the release of DirectAdmin 1.661.

Highlights of this release is a new tool for detecting and fixing database definer issues and new directadmin service process manager.

Full release change log can be found here:

DirectAdmin 1.661​

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!
 
The docs were updated shortly after forum post. But docs system is using cache extensively so sometimes even after the update, changes are not immediately visible until forced reload is performed.
@Zhenmue DirectAdmin and CustomBuild does not perform CSF restart as part of update procedure. It must have been triggered manually.
 
fln said:
The docs were updated shortly after forum post. But docs system is using cache extensively so sometimes even after the update, changes are not immediately visible until forced reload is performed.
@Zhenmue DirectAdmin and CustomBuild does not perform CSF restart as part of update procedure. It must have been triggered manually.
Click to expand...
directadmin update, has been running for like 10 hours already, and still going.

and no, no manual restart of CSF.
 

Attachments

  • daupdate.png
    daupdate.png
    41.3 KB · Views: 34
A small update is released to fix WordPress Manager and DB Manager integration.

@Zhenmue the screenshot shows CustomBuild updating 3rd party system components it is not the same as DirectAdmin update. I would recommend checking the process list to see where CustomBuild script is stuck. If you still have problems with if please open a support ticket. This seems to be a local problem.
 
2024:03:21-17:33:18: Error reading from 0.0.0.0: Cannot find first space after where GET or POST should be<br>
after updating , maybe related to this ?
 
I just notice that in error.log. In access log, for example, 2024-Mar-22.log:
22/03/2024:03:14:15 0.0.0.0 BAD REQUEST unknown
22/03/2024:03:14:15 0.0.0.0 BAD REQUEST unknown
22/03/2024:03:14:15 0.0.0.0 BAD REQUEST unknown
22/03/2024:03:14:15 0.0.0.0 BAD REQUEST unknown
22/03/2024:03:14:15 0.0.0.0 BAD REQUEST unknown
22/03/2024:03:14:15 0.0.0.0 BAD REQUEST unknown
Click to expand...

Also, is it a bug that I cannot turn off multi-server setup?
 
  • Like
Reactions: fln
gate2vn said:
Also, is it a bug that I cannot turn off multi-server setup?
Click to expand...
Confirmed. Tested on another server. With 1.660, I can turn off multi-server setup. On the same server, just after updating to 1.661, I cannot turn off multi-server setup anymore. Different servers, different OS.
 
Same issue with the 0.0.0.0 , only after updating to f33c77b0b929eae503eff47ec1bd9ae8b656d4a1
The 1.661 update before did not have this issue.
 
  • Like
Reactions: fln
Thanks for reporting it @Active8, @gate2vn, @ericosman. The error in the logs is harmless and was a side-effect of the new process manager terminating a no longer used process (for example on DA restart). And update is released to silence it. It also includes fix to multi-server setup ON/OFF toggle.
 
Evo skin, at user level. Using search bar on top, I cannot find any email user. Is that a bug?
 
@gate2vn, on our test servers search for email accounts works as expected. Opening a ticket could help us check if this is something that affects only your server.

One more update is released - it fixes a regression on Enhanced skin when creating new databases.

Starting DA 1.661 Enhanced skin is now using new database management system, so most DB related operations on Enhanced will now be executed much faster compared to previous DA releases :).
 
fln said:
on our test servers search for email accounts works as expected.
Click to expand...
Found the reason. If in the user package, I choose All Commands in Feature Sets, then the search is able to find email accounts. If I choose Allow Selected Features, and then even with all 3 options: Core, DNS and Email, then the search is not able to find any email account.

Can you check again and verify it? I assume that when I enable Email feature set, the search should be able to find email account. Any specific command for searching email account which I need to enable, if I choose Core and Email feature sets only?

P/S: talking about Evo skin, Refreshed layout.
 
For the dashboard search to work user needs access to CMD_AJAX_SEARCH command. None of the default feature sets has it. It is not something that has changed with this release.
 
Still having that issue with the '-no-header' at line 348 in scripts/letsencrypt.sh where cert renewals fail because of a non-existent parameter to 'ss'.

Also still having TLSA records that not seem to get updated after letsencrypt renews certificates. This actually results in customers moving away to office365 because every 2 months mail bounces for a few days because of the old tlsa records.

Am I the only one having there problems for months or did I miss something? <insert confused selfie>
 
You must log in or register to reply here.
Back
Top