Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature currently requires accessing the site using the built-in Safari browser.
If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread: CentOS2Alma discussion
Maybe too late for the topic starter, but seems reasonable for those who will face the problem on dist-upgrade.
I’ve had the same problem as described in the original post and the problem was in Apparmor.
Just check /var/log/messages file for errors.
AppArmor is installed and enabled by default...
DCOM directly is not used by Plesk itself and we have tested main Plesk scenarios with applied changes.
However, it may be used by hosted websites, and this action may somehow affect its functionality.
ASP, ASP.NET as well. Of course, it depends on the code and used components.
Disabling DCOM...
Unfortunately, Microsoft does not provide hardening recommendations for the issue due to architectural implementation in operating systems. Their official recommendation is "Using Windows Server 2019 would mitigate this attack vector".
vkleinhenz, thanks for reporting.
I was able to reproduce the problem in our local environment. The issue is reported to development team as PPP-21577 for your reference.
Also, adding directive
ProxyErrorOverride on
into Additional Apache directives (Domain -> Apache & nginx Settings) solved...
For Plesk 12.5 version use following command to manage SSL protocols:
plesk bin server_pref -u -ssl-protocols
To manage SSL cipher suit:
plesk bin server_pref -u -ssl-ciphers
I your case it should be smth like
plesk bin server_pref -u -ssl-protocols TLSv1.2
to use only tlsv1.2 protocol...
There is no problem with systemd, but we recommend first perform dist-upgrade to distinguish problems called by dist-upgrade itself and switch from sysvinit to systemd if you wish.
Problem with ioncube is known and will be fixed soon.
Incorrect unit permissions will be also fixed.
thanks for...
there is preparation script which will perform all necessary steps before dist-upgrade:
/usr/lib/plesk-9.0/distupgrade.helper.deb7-deb8_pre.x64.sh
then (dist-upgrade itself):
# aptitude update
# aptitude upgrade
# aptitude dist-upgrade
(you may try to use apt-get instead but you may get errors...
Of course the only psa-pc-remote milter should be removed from non_smtpd_milters, and the fix will remove only one for plesk 12.0+
excluding psa-pc-remote milter (inet:127.0.0.1:12768) from non_smtpd_milters is the exact correct way!
Everyone who have psa-pc-remote milter in postfix...
It happens because "default certificate" value is set on domain creation by default.
If you change "default certificate" to "not selected" on domain hosting settings you'll get behavior compatible with plesk 11.x - certificate assigned to IP will be used.
I've submitted report to development...