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

    How to stop logging of succesful logins to Courier Imap

    Thanks for your answer. I think you were right. It seems to be a problem with my current logwatch configuration. Before the update it did not contain the LOGIN information but now it does. So probably it is more a problem of my logwatch configuration.
  2. M

    How to stop logging of succesful logins to Courier Imap

    Hi, since the update to Plesk Panel 11.5 Courier Imaps logs every successful login to mail.log. I have tried to disable the logging by setting DEBUG_LOGIN=0 in imapd and imapd-ssl config file but this does not work. Has the configuration changed and how can I get rid of this log messages...
  3. M

    Update fails with message "ERROR: The product wit ID plesk ..."

    Thanks for your mail. I have tried the option --show-all-releases and it gives the following output: File downloading products.inf3: 100% was finished. File downloading plesk.inf3: 72%..100% was finished. File downloading pp-sitebuilder.inf3: 11%..23%..35%..46%..58%..70%..81%..93%..100% was...
  4. M

    Update fails with message "ERROR: The product wit ID plesk ..."

    Yes I tried it with exactly the same result. It was called with the following parameters: /usr/local/psa/admin/sbin/autoinstaller --select-product-id plesk --select-release-current --reinstall-patch --install-component base These are the same that are used by the daily cron job that was...
  5. M

    Update fails with message "ERROR: The product wit ID plesk ..."

    Hi, since some weeks I had the problem that the update from the web interface failed with timeout error, so I performed the Update from version 10.2 to 10.3.1 manually. The update worked fine and without any problems. But the problem with the timeouts persists and also the nightly run of the...
Back
Top