Search results

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...

There is no Security Advisory provided by Microsoft. You can contact MS support for the question.

In general, there should be no issue if you re-enable it from registry. At least, we haven’t faced with such issues.

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".

error description? some details would be useful. Try to inspect webserver and vhost logs.

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...

Here is the article about how to create custom error pages: https://kb.plesk.com/en/5279

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...

It looks like your installation was not fully completed. check autoinstaller logs for errors.

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...

Most probably you have the same issue.

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...

fixed in MU#6

Please, look into PM

reported to development (PPP-10678 for your reference)

remove whole non_smtpd_milters from postfix main.cf in case you do not use commtouch. If you would like to use commtouch then you can remove only "inet:127.0.0.1:12768" from non_smtpd_milters. restart postfix.

could you show me the output of the following commands: # /usr/local/psa/admin/bin/mail_handlers_control --list # readlink -f `which sendmail` # dpkg -l (for .deb like OS) # rpm -qa (for .rpm like OS)