Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Dear Pleskians! The Plesk Forum will be undergoing scheduled maintenance on Monday, 7th of July, at 9:00 AM UTC. The expected maintenance window is 2 hours.
Thank you in advance for your patience and understanding on the matter.
We have a bunch of servers on both Onyx (17) and Obsidian (18) on CentOS 7 that have begun logging entries like this in syslog:
wdcollect: Failed to connect to database server: SQLSTATE[HY000] [1045] Access denied for user 'admin'@'localhost' (using password: YES)
sw-engine-pleskrun: PHP...
Unfortunately that doesn't work. The issue is that while that does allow you to have an LE cert issued to an alias, it attempts to order the certificate for the primary domain first with the alias as an alternate name, so when the primary fails (because it isn't pointed at the development...
Anyone know a way to work around Plesk trying to get an LE cert issued for both the primary domain and the alias? For a website under development, the primary site may be pointed elsewhere, but it needs to be defined in Plesk with the real domain so the paths, email addresses, etc. are all...
Can someone tell me the command line equivalent to going into:
Tools & Settings -> Server Settings -> "Force daily log rotation for all domains" and setting the log rotation count?
Following up my post, it appears blacklisting psa-proftpd-1.3.6* in yum.conf will keep autoinstaller from reupgrading it. I'm waiting to hear from support, and they the developers, on whether this is safe to do or not.
The change in proftpd 1.3.6 is fairly crazy; it does a per-character read of /etc/group, multiplied by every file in a directory, as it builds the output. So if your /etc/group is a kilobyte, and you have 10,000 files in a directory, it's going to do a minimum of ten million read() function...
Was able to force it back via rpm -Uvh --force http://autoinstall.plesk.com/PSA_17.5.3/extras-rpm-CentOS-7-x86_64/opt/hosting/proftpd/psa-proftpd-1.3.5d-cos7.build1705170314.14.x86_64.rpm
Of course, not sure if Plesk will re-up it at some point; perhaps can blacklist it in yum, but not sure if...
Any progress on this ProFTPd issue? Applications don't always let you choose where they store certain files. It isn't practical to tell every customer who has updated from 17.5 to 17.8 that they should now rearchitect their websites and web apps around Plesk's use of a version of ProFTPd with...
Seeing same issue; psa-proftpd-1.3.6-cos7.build1708180220.17 takes nearly five minutes to output the contents of a 200,000+ file directory, ls -al takes 3 seconds.
This is not going to be possible for you. Based on your plesk -v output, you're running CentOS 5 which is based on an OpenSSL version which is incapable of TLS 1.1/1.2. You'll need to upgrade to a later version of the OS unless you want to risk overwriting the OS version of OpenSSL, but...
Just wanted to let everyone know about a bug I've encountered with our first instance of 17.8 testing, on CentOS 6. If a subscription has its shell set to chrooted, even if you've overridden the shell to use for cron jobs, all your subscriptions' cron jobs will be set to a chrooted shell when...
We're attempting to migrate domains from a Plesk instance which I suspect is inside a virtuozzo container. Many of the typical /usr/local/psa/ files are missing and the web interface looks unusual. We have root access to the VM but that doesn't appear particularly useful given the lack of...
Just FYI, that table is wrong; from the PPPM-1155 at What do the domain status codes in Plesk mean? the table correctly goes from binary 4 to 8 but incorrectly reflects that as a decimal jump from 4 to 16. All the additional decimal conversions are off by one base2 digit. Someone pointed this...
Hello, I'm running into an issue with 17.5.3 when attempting to force TLS 1.2-only, which PCI requires in June. If Postfix is set to TLS 1.2 exclusively, roundcube can no longer send email:
Apr 5 01:48:07 server postfix/smtpd[6952]: warning: TLS library problem: 6952:error:140760FC:SSL...
For a transactional site, caching doesn't help; any interruption to the application results in potential lost revenue, so the kind of sites I'm talking about even a few seconds for an SSL-related restart could cost money. We do HA manually to get around that, but anything to make life easier is...
Just regular kernel and hypervisor updates are generating enough downtime to create problems these days, then you add in downtime from customers who want to do something like Lets Encrypt so web server restarts are occurring every 90 days for every site on a given server (all of course on...
In our case the shared filesystem would be implemented on top of redundant enterprise storage, whether that be hardware-redundant NFS, or two VM's using a cluster filesystem on top of multi-path block storage, so either way that would not be the concern. The database would be one, and haproxy...
Thanks; just added vote and comment there. I have a feeling this is going to be a bit too far from the needs of Plesk's normal customer base to make it attractive for them to develop. There's so many factors that go into an HA solution, and choices that may be good or bad from one entity to...
Curious if there is anything on the roadmap for a version that implements any type of HA features, such as managing multiple servers and then we provide the load balancing on the front end? Example; Plesk manages nginx/apache config across two servers so SSL updates, etc. happen on both, we...