Search results

CentOS 6 will not go beyond version IPtables 1.4.7 Whereas F2B v0.9.3 uses functions that are only available from at least IPtables 1.4.20 I had the same errors as you see (the -w switch thing) I first tried downgrading with yum. Wouldn't work unfortunately. Best way to go (worked for ALL of...

Is there anyone out there who can tell me how to do following: We love the way Plesk handles WordPress. However, I also want to have some extra plugins available when installing WP (mainly some security related plugin and a default .htaccess modification for XML-RPC issues. This will save me a...

What gbotica is suggesting is correct. But just restarting fail2ban will most likely not help in all cases, depending on versions of OS. Version 0.9.2 still ran ok on our CentOS 6.7 systems untill last week. The big problems began when Fail2ban upgraded to 0.9.3. We use F2B with Iptables. There...

I guess I did get this popup. But I already removed some domains before, so got a little automated. Then finally I must have clicked the wrong red-cross and ignored the popup and the slightly different text. In 9.5 there was not a pop-up, but an undenyable new screen with a listing of everything...

I will try to come with a compilation soon. currently still too busy migrating machines.

Well, i finally had Plesk support successfully fix this problem. There were several database inconsistencies. No idea what caused them. This was a freshly installed machine (ran only 2 weeks) migrated from 9.5.4 and added 3 new clients to it. All problems came up after applying patch #16, Sept...

I have migrated recently from 9.5.4 (rockstable !) to 11.5.3 (sorry, still buggy). Have been using Plesk since Version 1.3 It is a nice interface, but it costs me, as a hosting provider, very much time to learn to use it again. I miss many features, or they are hard to find. Biggest...

After applying patch #16 today, I now got following error in Plesk Panel: New configuration files for the Apache web server were not created due to the errors in configuration templates: Template processing failed: file = /usr/local/psa/admin/conf/templates/default/domainVhost.php, error =...

Let me join this conversation as I have this problem too. However, only on 1 of my currently 3 Plesk 11.5.3 servers. correction: now 2 of 4

Perhaps you do not want to hear this: I use plesk since 2001 with Qmail. Tried several times on Plesk with PostFix, because I love postfix (use it on our spamfiltering cluster). But I removed it from the Plesk servers again :( Simply it gave me too many problems if all different kinds. My...

Not for me. Installed fresh new system with CentOS6.4. Plesk all latest updates. Migrated some domains/clients from 9.5.4 server. simple Pleskbackup command: /usr/local/psa/bin/pleskbackup --server --output-file='odysseus.dump' This returns: Runtime error: The backup failed with errors!

solved... Well, it seems the problem solved itself.... Now, almost 24 hours later, I click "updater" again and there is no problem anymore... Als updated ok. Possibly there were some files locked or in use by a process.

use Atomic repo You should activate Atomic Turtle repo: see: http://forum.parallels.com/showthread.php?t=81843 I use it without any problems one several servers. Please note: exclude mysql from the repo if you do not wish to have it upgraded.

PRODUCT: Plesk 9.5.4 on Centos 5.4 x86_64 Trying to update through GUI. On my other (identical) servers no problem. But this one particular server keeps saying: Unable to obtain the latest version of Parallels Products Installer: The required version '3.11.0' was not found on the server...

Is it resolved yet? I got customers complaining about not being able to login.

same here Also over here still no success. We'll stick with 9.3 for the time being. Also in K.A. upgrading a key to 9.5 fails. It's strange that Parallels cannot fix such a problem in 2 months of time.

I would strongly advise to upgrade to 9.2.1 at once and skip the 9.0.x versions, as it is buggy and may break things. Personally I am waiting a little longer with upgrades. There are no security holes and 8.6 is rock-stable, so why upgrade?

It sounds like a wise plan the way you describe it. You can always easily revert back to 8.6 I just would skip the upgrade to 9.0.x. And upgrade to 9.2 right away, because upgrading to 9.0.1 is known problematic.

user permision problem. Seems like a user permission problem. Probably this would make it possible for you to update: /usr/bin/freshclam -u root I see your freshclam.log is owned by user qscand and group qscand. And most likely the system thinks it is user "clamav" So edit...