Search results

I'm a long-time Plesk (and Parallels and Ensim before that) admin for shared hosting. I always use Linux servers. I have been looking at Plesk 12 and 12.5 over the last year or so, and ran some tests with disappointing results. So I stayed on Plesk 11.09. I just brought up a new AWS virtual...

gbotica gave instructions on how to apply on RedHat/CentOS. But I agree, the first article shared wasn't helpful - no instructions on how to apply this to a server running Plesk and some Linux variant that is supported, like Ubuntu or CentOS. I really don't feel like applying a patch manually...

Thanks, that what I was looking for ;-)

It is safe to update on CentOS 6 and Ubuntu 14 when Plesk is installed? If you don't know what I'm talking about, read this: Extremely severe bug leaves dizzying number of software and devices vulnerable - arstechnica.com...

The whole interface changed to the new Plesk 12 interface, from what I'm used to on Plesk 11, without my permission. A trip to Tools & Settings -> Plesk Appearance -> Interface Management and selecting "Service Provider view" and "Open hosting operations in Server Administration Panel" set...

I see I will need to go through each option at a time, comparing to my settings on Plesk 11, to make sure everything is kosher. I suspect other things have changed too. I did all of this already, when I first set up the server and installed Plesk 12. Still no idea why a bunch of stuff changed...

OK, I tried the "poweruser" command, and am making progress. btw the command I used that worked was: ./poweruser --on -simple false -lock false But the Email function is still not there. Turns out, "Enable mail management functions in Plesk" was turned off somehow? Under "Tools & Settings"...

I just set the Ubuntu "root" user password. Then logged into Plesk with user "root". Same problem, still no administrator rights. It still sees me as the same user as the "admin" login.

I was trying out Plesk 12 on Linux - Ubuntu 14.04 LTS, with a trial license. Long-time Plesk (and before that, Ensim) user. I have two other servers running Plesk 11, on CentOS 6.4. Everything was going fine. The trial ran out. I purchased a Web Pro license (no reseller support) and installed...

The sites-enabled directory is present on Ubuntu, not on CentOS. I trashed the server, used a clean Ubuntu 14 AMI image, ran the Plesk installer and see that directory now. However, the site is still using the wrong (default) folder, not the one specified for the site. I did verify the...

This is the KB article that outlines what I did: How to deploy Plesk 12 on the Amazon EC2 service http://kb.odin.com/en/122222 It specifically says to use the Plesk 12 AMI image, as the installer is not supported on Amazon. I used the "Plesk 12 'Bring Your Own License'" AMI, which is one of...

What you're saying doesn't make sense to me. First of all, the AMI I used comes directly from Parallels, Inc., now called Odin. So you make the AMI, but don't actually support it? You tell me it is broken? but Amazon doesn't make the AMI, Plesk does. So you guys installed CentOS, installed...

OK, I did all of that, I hope it helps. I zipped it all up into a single file. [root@cloud03 ~]# zip directories-and-conf.zip apache-directory.txt nginx-directory.txt httpd.conf nginx.conf adding: apache-directory.txt (deflated 81%) adding: nginx-directory.txt (deflated 81%) adding...

Neither of those exist: root@cloud03 vhosts]# locate -i "default.conf" /usr/share/alsa/pcm/default.conf /usr/share/sw-collectd/postgresql_default.conf [root@cloud03 vhosts]# locate -i "default-ssl.conf" [root@cloud03 vhosts]# the two "default.conf" are for alsa (sound) and postgres (DB), not...

And I am using NGINX, just like I do on Plesk 11.

UFHH01, I did a locate and neither "sites-enabled" or "sites-available" are found on the system, so I don't know what you mean there. root@cloud03 vhosts]# updatedb [root@cloud03 vhosts]# locate -i sites-available [root@cloud03 vhosts]# locate -i sites-enabled [root@cloud03 vhosts]#

I have dozens of sites running on Amazon AWS across multiple Linux servers, all running Plesk 11. But I can't upgrade if Plesk 12 is broken.

Long-time Plesk user (and Parallels and Ensim before that). This is my second attempt to test Plesk 12, with the same result - I add a brand new site, but my changes to the site web documents have no effect. I found that regardless of what the Apache configuration shows for the site, it is...

Thanks IgorG, good info. A second bash patch is out. CentOS 6 has the update already. To update: yum update bash To update just bash on Ubuntu, these are the commands: I'm still not convinced this is the last word on this. Some are showing even the second patch has an exploit that works...

BTW apparently the "site" command could have also been used. But like I said, this script works, I just ran it on multiple servers. Usual disclaimer - Use at your own risk. If you don't know bash or scripts, this would not be a good idea for you to try. Just use the GUI (and take forever).