Recent content by TurabG

Thank you for taking time to concern. It's not an attack, it's a regular bot visit that I can see on the stats. To be exact, one named "feed" in the bot list caused most of this traffic. For 3-4 months, the traffic was between 500-700GB regularly. And they didn't cause any black-outs on the...

Well they do; as I can see them in Awstats and I don't see them when I block the known bad-bots IP block. After I had done some blocking, the traffic dropped back to approx. 30-40GBs. By the way, as I said before, I have blocked some large IP pools of some cloud services like Google's...

I have a firewall in front of the Plesk web server. (Endian Community) My web server is not very active, it has only 10-15 sites whose traffic shouldn't be more than 40-50GB monthly but I see 500-700GB traffic due to "bad bots". So from time to time, I go to Fail2Ban interface to look for IP...

Well yes but this implies it always runs on default config. I can't make any changes. When I run nginx command on shell, it says: nginx: [emerg] bind() to 192.168.xx.xx:443 failed (98: Address already in use) When I check status of the running process: systemctl status nginx ... .. .. nginx...

Yes they are the same local IP which shows up in Plesk panel and ifconfig output. But what port do you mean which another service could be using? 443? No, not possible, sites are working. As you know, Plesk has both Apache and nginx simultaneously and nginx is used as a proxy. Since the websites...

docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255 ether 02:42:40:a7:73:94 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0...

I elevated from Centos 7.9 to Almalinux 8 using the Plesk elevation script. Overall process was quite fine. I am just having one issue which shows up in Website Configuration Toubleshooter. It says: nginx: [warn] conflicting server name "_" on 94.xx.xx.xx:443, ignored nginx: [warn] conflicting...

I don't think absence of DKIM would cause "relay access denied" error as default mail setup in Plesk doesn't include DKIM and it works well normally. So I am pretty sure the problem lies elsewhere. I couldn't fix this issue and I moved to Yandex 360 rather than using Plesk for hosting the mail.

Oops, didn't notice the editing, could have saved me half an hour :) Thank you too.

It's been more than one year but since it remains unanswered, I will reply to this old topic. I had the same problem and didn't find anything which even mentioned this specific problem but only this topic. So I dug a little more and saw the KB article which told Plesk command line utilities...

Now checking the other suggestion you made; I had already tried it before. (My first post, article 3). And I have tested disabling blacklist check altogether; it's not an issue about it. We can easily confirm it because when sorbs list was active, maillog was showing "spam" error; but when I...

Well, in fact it actually was like that when you asked. Then I tried to change it to "defer" instead of "reject" as I saw this suggestion in Plesk forums. This directive must have reverted back to "reject" when I ran "plesk mail repair". Either way, it has no effect on the behaviour and no...

I will try the other suggestion you made. In the mean time, I looked for that directive in my main.cf but it is absent all together. There are other restriction directives liek: smtpd_sender_restrictions = check_sender_access hash:/var/spool/postfix/plesk/blacklists,permit_sasl_authenticated...

And that's exactly what I wrote in the subject of this topic. Here is the detail: Jun 17 12:04:20 lin1 postfix/anvil[27938]: statistics: max connection rate 1/60s for (smtp:52.55.244.91) at Jun 17 12:00:59 Jun 17 12:04:20 lin1 postfix/anvil[27938]: statistics: max connection count 1 for...

Yes. It shows the default settings of Plesk DNS like mail.anotherdomain.tld and it points to this server's IP and mail health shows no errors.