Search results

Probably you had this set to NO for some reason, maybe because you had SMTP_BLOCK=0 and had it that way to prevent this setting to be overwritten on a DA update. Da only updates CSF if the csf is set to yes in options.conf file.

Well the apache logs are not the most interesting as they are the easiest to save, that is not really a problem. It might also be the least interesting as this is visiting logs, not really something the user might be doing themselves. But the exim mainlog and maillog doe not contain any mails...

In the EU we have a new law called E-Evidence Regulation and Directive. The Regulation lays down the rules under which an authority of a Member State, in criminal proceedings, may issue a European Production Order or a European Preservation Order and thereby (directly) order a service provider...

Please use the "Like" button for thanking or acknowledging instead of upping an ancient post.

Yes one time, see answer above, next time please ask your hosting company as this forum is inteded for support to Directadmin license holders only, so admins and resellers. Not hosting customers. ;) Unless you're the license holder ofcourse. :)

Ah oke so if backtrace present than crash. So the stackdump line is not required. In that case only 2 of 4 servers had no issues because only 2 server I had no backtrace. Luckily I used the update, everything is running 4.98.2 now. I only see now from yesterday before I updated. Things look...

Maybe not all AlmaLinux versions or installations? I've got Alma 9 and do not have any stackdump lines or crashes when issueing that command. Not on any of our Alma 9 servers. Only have like this (if any) 2025-11-14 18:08:58 backtrace 2025-11-14 18:08:58 --- 2025-11-14 18:08:58...

This looks not good. Got error 'PHP message: PHP Strict Standards: Non-static method PEAR::setErrorHandling() should not be called statically in /home/homedir/domains/domain/public_html/webmail/program/include/iniset.php on line 122\n' [Fri Nov 14 02:23:07.668115 2025] [proxy_fcgi:error] [pid...

Probably you can do it via the Custombuild GUI, but I always work via SSH as root. So as root you should be able to do it like this. da build set modsecurity no da build update da build list_removals da build remove_items That should remove it properly.

Exactly the reason I have a password on mine. If they get stolen it might be able to compromise servers. If they now get stolen, they still have to find out the password, which is by the way also not the easiest one. ;)

No you have a different problem. This here is an rDNS/PTR issue because that error is thrown and it's on outgoing mail. You might have an exim issue on incoming mail, it's different and not rDNS/PTR related otherwise you would have seen that error too.

If you created that in Directadmin it won't be seen as a valid PTR record because PTR records need to be set with the ip owner. You need to set that PTR record where you cat the ip address from, mostly your datacenter.

Yep I don't mind, but whatever the solution is, either more personal or more diradmin@hostname, it should be fixed decently. ;)

First of all, thank you for adding the CSF/LFD change to the DA version changelog. It's about LF_INTEGRITY and PT_LIMIT. This sounds a little bit confusing to me: So first line. Configuration in existing servers will be updated with this Directadmin update. Am I correct in the assumption that...

Agreed but it should easy to provide the local to external mail for resellers. Which is probably the reason initially in the past the usage of the contact e-mail address was programmed in there. At the early days that didn't matter. Now it does matter and resellers are used to have this working...

I had the wrong line, but that it has no difference to the solution was not my intend to write it. As sais, this is the reason for my writing that line. Easier/shorter and prevents typo's.

and Normally no need to replace, just use /usr/local/directadmin/scripts/letsencrypt.sh server_cert which is the correct command according to the docs and the script will autodetect the correct hostname which is provided to DA. Will prevent typo's too. grep -Fvx "$(da config-get servername)"...

I didn't mean an external account. But if my reseller account is on the server like [email protected] then I'm normally able to send messages to my customer from that mail address. So in these kind of years, things change but also technologies change and it should be possible (just like with...

Yes why not? Alma 9 will only be EOL in 2032 so time enough to run with it.

Well I disagree a bit here. Because if a reseller, let's say me, creates a new user account, it would be nice if this user will get this mail from my contact e-mail adres and not from diradmin@hostname because that might be confusing to some users. I wonder how CP is doing that, can't remember.