Search results

After loads of experimenting, I found the solution. I went to Tools & Settings -> IP Addresses. I clicked the IP address I was having a problem with. The default site was set to None. I selected the correct site and clicked "Ok" . That alone did not fix the problem. After that I ran...

I am running Plesk Onyx 17.8.11 on CentOS 7.6.1810 I had a website that had been deactivated and today I reactivated it in an attempt to test software updates on it. When it was restored it was on a shared IP address. I moved it to a dedicated IP address so I could directly access it by IP...

After hours of trial and error (mostly error), I stumbled across the solution. I tried disabling the firewall just in case but that didn't work. I tried disabling Spamassassin but no change. I decided to change the SMTP server from Postfix to Qmail to see if that would work. I tried another...

I managed to get the warning fixed but mail will still not deliver (inbound). Outbound mail works. Is there any chance this could be a firewall related issue? Or some kind of security feature?

This is a new problem for me. This is a new server running Plesk (not my first Plesk system) and I have a problem where inbound mail stays in queue. I've attempted to flush the queue and no luck. I've done the mailbox repair command from the command line with no luck. I've checked DNS...

Sorry Jan but I am not sure you are much help. I know Plesk doesn't make fail2ban and csf. It doesn't make Apache, PHP, nginx, etc. But it does work with those services and when there are problems related to those services working with Plesk people post here. Don't you think I've hunted high...

Hi Jan, There was no error in the fail2ban.log. It was disabled as if I had done so through Plesk. CSF disabled it and never re-enabled it. So late last night/early this morning, there was another CSF update. This time it wasn't a clean shutdown with no errors. This time the log file was...

I MAY have found a possible problem. Once again I noticed that fail2ban was off when I went into Plesk. Didn't make sense that my script didn't restart the service when it crashed. So I checked the logs. It didn't crash. It was shut off. I noted the time it shut down and remember getting a...

Until this problem is fixed, I have added some protection to the server. I have a cron job that runs every 2 minutes to check if fail2ban is still running. The service gets restarted if it has failed. This isn't the ideal solution to the problem. Ideally the service wouldn't stop for some...

Unfortunately the problem is back. Frustrating to say the least. Fail2ban is set to automatically restart if the service crashes, so I am not sure why it isn't restarting in these cases. Seems more like a shutdown of the service than a crash. I tested it out. If I kill the fail2ban service...

As of now Fail2Ban seems to be running without any kind of errors. Two changes were made and I am not sure why solved the problem. I suspect the change from multiport to allports in the Fail2Ban configuration file solved the issue. But I also updated jail.conf as I mentioned earlier. Not...

Thanks for the reply. Fail2Ban was running. It may have been restarted since those errors appeared in the logs. I also edited a Fail2Ban config file (name slips my mind) and changed the rules from multiport to allports. I went to install python-inotify and apparently it was already installed...

Here is the output of iptables -L Took a few minutes to run.

Thanks for the reply. Fail2Ban should be compatible since it was installed/activated using the Plesk control panel. Before I start messing with more settings on the server I will provide as much info as possible related to the questions you asked in case there is something obvious that I am...

I really wish people would quit marking things resolved when they are not. Problems are ongoing. The reinstall did not fix the problem Fail2Ban continues to spew errors and it is only a matter of time before it shuts off again. Here is a sample of errors in the log. Maybe someone can make...

I had uninstalled and reinstalled Fail2Ban shortly after posting that last post. So far the service has been running without a problem. A week solid as of now. I'll give it some more time and if that does the trick I will mark this thread as solved.

Ok Kernel update did not solve the problem. I'll post the logs. Maybe someone can figure out why F2B keeps shutting off. 2017-09-05 01:47:17,065 fail2ban.action [2103]: ERROR iptables -w -D INPUT -p tcp -m multiport --dports smtp,smtps,submission -j f2b-plesk-postfix iptables -w -F...

I am going to mark this as solved for now. Since the kernel update, Fail2Ban has banned 4 IP addresses and hasn't crashed. I will reopen this if anything changes.

I would like to add that I have virtually identical setups on two different servers and this problem only happens on one. Additional note: I've performed a kernel update in case the problem was related to that.

Can't believe I forgot to check in here. Here is something from the log file. Don't know if it helps at all. BTW at this time there is only one banned IP in this module. 2017-08-12 17:38:37,425 fail2ban.action [23141]: ERROR iptables -w -n -L INPUT | grep -q 'f2b-plesk-postfix[...