Search results

Kind of - it still wont offer clustering of web customers or the panel itself. Its really just mail, dns and DB which you could have already done anyways with a little work. Until they actually get true clustering (web customers mostly but the panel as a close second) it may not be worth it...

Thats a bummer! Do you have any technical info or specific error messages that you can provide for us to assist in troubleshooting?

is this a VPS? If so try this http://www.r00t.gr/openvz-rsync-problem-fixed/ otherwise its likely that something is running out of space, try doing a df -H maybe one there is a disk on a mount point in there somewhere running low on space.

Sven, no it means that if the customer has a dedicated IP already then it will use his IP to send the mail. This doesnt require you to do anything or purchase anything. Its a basic protection that is now in Plesk that will allow you to put a user on a dedicated IP (for w/e reason) and then if...

You can grant the permissions pretty easily grant SUPER on *.* to 'user'@'localhost' identified by 'passwordHere'; Then flush privileges and you should be good to go.

I just wanted to reply that this is in fact the answer - I ran into the same problem today and used these steps to fix. go into the server via SSH and enter MySQL Then use the query to find the domain name that is bad SELECT d.id, d.name, R.rep_id...

and even then I would serisouly think twice about doing that.

I think thats because several domains have been enabled for SSL and typically you have one domain, one cert per IP. You can ignore that error in that case.

You can also add the cononical link in your code, its good SEO to do that anways or you can add in .htaccess that redirects

you could try using clam av or some other anti malware program to scan and remove the files. If you have backups of the client files, that would be preferable I would imagine.

There are a few things you can try - run php as a dso instead of fcgi/cgi as it uses more memory for the cgi/fcgi, dont use suphp (or any variant), disable httpd modules you dont want/need, set rLmits for memory usage, use suhosin so users cant specify high memory usage in ini_set function calls...

Yes, you can check this file as such You can use this command to install them if your not at the latest version

are you the server owner/operator, or a customer of the plesk server operator? If you are the client I would advise you to contact your provider to get the ftp server settings. if you are the owner/operator, go to the server and try and login manually in the local ssh terminal and see what...

From what I am reading in your post it looks like you are trying to initiate it from the source server and not from the new target server, is that right? if so have you tried (or can you try) using the plesk migration manager and starting the migration from the new server instead via the GUI?

For Web Admin, make sure you dont have a pop up blocker because it will open it in a new window, so it could be blocking the pop up and just refreshing the page. If you still cant do it, you can always install a temp copy of phpmyadmin in your domains web space and then login manually that way...

I see there is a feature comparison about what Plesk offers over cPanel in this doc https://parallelsnetwork.com/wp-content/uploads/2012/05/Parallels-Plesk-Panel-11-vs-cPanel-111.pdf But is there one that exists the other way - as to what features cpanel offers that Plesk still doesnt yet...

I dont believe that you can use anything other than a 9 license with plesk 9. Although php isnt a plesk thing so it comes with the OS you use, or a third party repo like art so you can install any php version you want no matter what version of Plesk you use. I would always recomend to use the...

from what I heard it is in RTM, but will be GA next week

none of this helped me, all I can find on line is that the customer may not have installed a proper war bundle - is there anything else that can be looked at?

have you tried using the migration manager to move the domains over to the new server? or maybe the CLI? /usr/local/psa/bin/pleskbackup clients-name [clients here] -v --only-hosting --skip-logs --output-file=clients1 Then test it on the new system after ftping it...