• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Security risk in updating Plesk

Token

New Pleskian
After updating Plesk in 'Database Hosting Settings' always is choosed 'Remoteverbindungen von beliebigem Host zulassen' ('Allow remote access from any host'), but I've choosed weeks ago 'Allow only access from local host'!!! Often after an update this settings are edited from Plesk to the default!! Thats a big security risk.
 
I can't reproduce this issue on my test Plesk 12.5 server. I set it to 'Allow only access from local host' and installed latest updates with

# plesk installer --select-release-current --reinstall-patch --upgrade-installed-components

The setting remained the same.
How I can reproduce this issue?
 
Back
Top