Recent content by Sander V

See subject. I've had this issue a few times now. The standard solution is to stop fail2ban, remove /var/log/fail2ban* and reinstall fail2ban. However, today it happened again and the above solution didn't work. Even removing /etc/fail2ban before reinstalling didn't work. I've determined that...

Today I updated Qmail through Plesk and sure enough, the bug still exists in the script. I'll see if I can contact the company.

I had the exact same issue myself, with qmail on Plesk 12.x and CentOS 7. Turns out /usr/local/psa/admin/sbin/mailqueuemng used the old way of starting and stopping qmail, by using the /etc/init.d/qmail script. However, this script does not exist anymore because of systemd. So I made a backup...

It has been a while, but are you sure there aren't any domain records with a parentDomainId NOT zero? This worked for me: SELECT * FROM `domains` WHERE parentDomainId != 0 and id in (select object_id from Subscriptions where object_type='domain')

Resolved it. The error message was exactly what it was: in the Plesk PSA database, there was a subscription record that pointed to a domain record that was actually a subdomain. After I removed this subscription record, the WordPress Toolkit did not produce an exception again. Running the mchk...

I recently upgraded to Plesk 12.0.18 (currently MU #10) from Plesk 11.5. Two problems arose: 1) In WordPress Toolkit, I'm getting the exception "Not a main domain of subscription". 2) Outgoing mail control is not working correctly, I have to keep it disabled or nobody will be able to...