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.
The APS Catalog has been deprecated and removed from all Plesk Obsidian versions. Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.
Hello,
We have a little script on our server which takes the internal plesk backups and sends them to some AWS storage.
My question is if we upgrade from 12.5 to Onyx are we going to have any issues? The only thing I could think might go wrong was if the directories for the backup locations...
Hello,
I'm looking to upgrade from Plesk 12.5 to Onyx, however we have some custom scripts which take our daily Plesk backups and send them to another server.
Has the backup process or directories changed at all in Onyx? I just want to make sure before I upgrade and find our backup scripts no...
Unfortunately no. I still get this message after every update. Would love to get to the bottom of this, but at the moment I run the command IgorG posted above after every update.
Please post back if you find anything
Thanks for your reply. I've just ran that and there were no errors, says patches were installed successfully.
The panel always updated or at least said it was on the latest patch, despite it saying it failed to update.
I'll see what happens on the next patch...
Thanks
Running Plesk 12.5.30 and every time I install the updates so #23 today for example, it says it failed, but when I refresh the page, the update option has gone and the version on the dashboard says it's running the update it apparently just failed? The failed bar still shows at the top till I...
It now seems to be disabled somehow, but having to change it in /etc/httpd/conf/plesk.conf.d/server.conf which means it'll get overwritten next time that file is generated.
Any ideas why it has to be placed in that file for it to work?
Thanks
Josh
Just done a little experience, created another server, same spec, Centos 6 with Plesk 12.0 with the same updates.
Created a dummy subscription, tested to see if TLSv1.0 was enabled for that website and it was. Did the exact same step as I mentioned in the first post, edited...
No I don't use nginx, I did try last time I had this problem following this guide but ran into problems - http://kb.odin.com/en/120083
Thanks for your suggestion, just tried it, restarted apache and unfortunately TLS1.0 is still enabled...
This is for normal domains using an ssl certificate.
I've edited the file /etc/httpd/conf.d/ssl.conf with the line SSLProtocol all -SSLv2 -SSLv3 -TLSv1 and restarted apache but TLS 1.0 is still enabled.
I've also ran /usr/local/psa/admin/bin/pci_compliance_resolver --enable all as mentioned...
That is a post from me a while back when I was having the same issue. I've repeated what fixed it last time from that post (updated ssl.conf) but that hasn't worked this time... I can only guess another file is overwriting it somewhere...
Hi,
My PCI compliance scanning software is failing due to the server supporting TLS v1.0 on port 443. The server is running Centos 6.6 Plesk 12.0.
I've updated the ssl.conf file with the line: SSLProtocol all -SSLv2 -SSLv3 -TLSv1 but it doesn't seem to have made a difference. I phoned up the...
Thanks Kristian,
Correct I'm not the admin of the Node Virtuozzo runs on so there is nothing I can do as my hosting company will not change it. I've spoken to the PCI compliance people who suggested closing port 4643. Would you know how to go about that? At the moment I am letting Plesk manage...
Amin Taheri I tried your suggestion about editing the /usr/local/psa/admin/conf/ssl-conf.sh restarted and the scans are still showng TLSv1 as supported.
I also tried adding -TLSv1 to the protocols in /etc/httpd/conf.d/ssl.conf and it made no difference.