Recent content by Gjimi

@trialotto Thanks for senseless useless texts :) you really littered my post and please don't write anything else here!!

Mail Server Certificate for mail.domain.tld is not created, otherwise I wouldn't be writing here.

Certificate for mail.domain.tld is not created, otherwise I wouldn't be writing here.

change virtual host from: <VirtualHost 138.xx.xx.xx:443 > ServerName "sytest.de" ServerAlias "www.sytest.de" ... to: <VirtualHost 138.xx.xx.xx:443 > ServerName "sytest.de" ServerAlias "www.sytest.de" ServerAlias "mail.sytest.de" ... then it works immediately. Let's Encrypt can then also...

So much chatter and fantasies here, it's unbearable. It has nothing to do with AAAA or BBBB, it has nothing to do with DNS, it's simply a false message from Plesk. I also explained why it can't work. And yes, ALL servers, ALL domains are affected. To reproduce it, it's very simple: add a new...

PS: If I create a subdomain mai.domain.tld in Plesk, it works, but it's not too complicated for customers.

example Domain: sytest.de You can see that all DNS are OK. Even *.sytest.de points to IPv4 and v6. Additionally, mail.sytest.de is also in DNS and points to IPv4 and v6. Both IP's are enabled in Plesk and otherwise work normally. But it's not a mail.sytest.de subdomain, so it doesn't have to...

Maybe your system settings are different, but there's no comparison. For example, we only have external DNS and no nginx. Check DNS? Yes, I'll wait for you to tell me :) I'm not a beginner! Everything's OK with DNS and Plesk, but selecting the new mail.dmain.tld function gives an error...

Wildcard is not used here because we have external DNS. It's already disabled by "allow-wildcard-certificates = false," but it has nothing to do with the problem here. Related to Apache, as explained above, Let's Encrypt cannot verify via http, which is why an error message appears...

Plesk has added a new option for creating Let's Encrypt certificates for mail.domain.tld. If you select this option (all customers do) you always get an error message stating that it is not possible to create a certificate for mail.domain.tld. Reason: Plesk does not create an alias (in Apache)...

it's been resolved, this was helpful if anyone has the same problem: apt-get remove --purge fail2ban then install again via web interface

I have reinstalled fail2ban, uninstalled via web interface, reinstalled via CLI, tried everything, it installed normally, but the /etc/fail2ban/ folder is empty, with no config files.

read before writing. Yes, but no IP can be seen

just none! otherwise the IP would have been blocked or Fail2Ban does it, but he can't because no IP can be seen, I wrote. Apr 11 15:43:39 96 plesk_saslauthd[14952]: No such user '[email protected]' in mail authorization database Apr 11 15:43:39 96 plesk_saslauthd[14952]: failed mail...

plesk_saslauthd is under attack, there are thousands of the: plesk_saslauthd[17936]: No such user '[email protected]' in mail authorization database plesk_saslauthd[17936]: failed mail authentication attempt for user '[email protected]' (password len=13) in the logs. (just something) no IP to...