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

Search results

  1. G

    IPv6 nginx bind problem

    I did not change anything on the console, though. At the moment no certificate and no website is set to the IPv6 adress, but the log still comes up with the same problem after reboot.
  2. G

    IPv6 nginx bind problem

    Debian 7.4 64, Plesk 11.5.30 Update #40 I have changed the server certificate and installed several ones to dedicated ips. Now nginx won't start correctly so that websites are not shown: 2014/04/10 03:08:50 [emerg] 2990#0: bind() to [xxxx:xxx:xxx:xxxx::x]:80 failed (99: Cannot assign...
  3. G

    Plesk and the heartbleed bug/ security vulnerability

    OpenSSL advises to update to G: https://www.openssl.org/news/secadv_20140407.txt And there is still a problem after rebooting now. Webs won't work until reconfiguring.
  4. G

    Plesk and the heartbleed bug/ security vulnerability

    OpenSSL was vulnerable before. I tried this test: http://filippo.io/Heartbleed/ I am using Debian 7 on two servers. The other one got an update from Plesk last night and is not vulnerable anymore. So it looks like Plesk has fixed it, too, via update. BUT I have the same problem on both servers...
  5. G

    Plesk and the heartbleed bug/ security vulnerability

    After restart my webs won't work. I set the ssl certificates to the ips and webs again, but no luck. Only /usr/local/psa/admin/sbin/httpdmng --reconfigure-all works. After a new reboot the problem persists.
Back
Top