DirectAdmin 1.665

Thanks for sharing you use case @nlaruelle.

The situation is quite tricky. We do not want to completely ignore file ownership change errors, because it could mask unexpected problems in various places.

It would be the best if you could enable file ownership support on the NFS server, but I assume server side is outside of your control.

Would it be possible for you could open a ticket and grant us access to the server with this problem? We would like to check what king of restrictions are applied on the NFS mount. Ideally we would prefer to handle such environment without errors and without adding extra configuration options to manually ignore errors.
 
A small fix is cherry-picked form the latest DA into DA 1.665 release. It prevents main server cert issue failure when an additional sever certificate domain is a wildcard domain that covers main server name.

Prior to this change, for example example having servername=server.example.net and acme_server_cert_additional_domains=*.example.net, would end up with an error from LetsEncrypt stating that *.example.net already includes server.example.net. The update detects such configuration end excludes server name from the certificate request when it is not needed.
 
fln said:
I assume server side is outside of your control.
Click to expand...

Thanks a lot! You are right, the complementary NFS Backup Storage offered by OVHCloud with their dedicated servers uses "root_squash" and does not allow the "chown" operation.
Our need is simply to have a .zip file for all the accounts.
The ownership of this data can be guessed from the filename of the archive? The previous behavior of DirectAdmin was suitable and worked like a charm. We hope not to reconsider all our second backup system 😅 Ticket #58908 was opened, thanks again !
 
Hi!

We are using the "stable" update channel (1.665) on our servers, and a security vulnerability was recently identified in RoundCube. The fix has already been implemented and is available in version 1.666. Could you please make this update available on the stable channel as well?

Thanks!
 
@fln since the update of DA showing these temp database users via one-click login these users are not deleted quick enough. Also they are being backed up when they are still there. So you get a lot of extra db users suddenly

Is there a way to hide them or not show them like before this change?
 
In the DA 1.666 release temporary users are not included in the backups. The 1.665 versions does have new SSO logic but still uses old DB backup system. So this problem is temporary (until next DA upgrade).
 
You must log in or register to reply here.
Back
Top