• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

Search results

  1. R

    Question Upgrade postgres

    I've installed PostgreSQL 13.3 on my server and haven't seen any issues with the Plesk DB integration yet. Table stats, connection info and user details are shown as before.
  2. R

    Question Upgrade postgres

    Thanks for the quick response, Igor! Yes, that's what I would expect, too. I guess my question was, what exactly would be missing if the Plesk-PostgreSQL-integration broke. It seems that it's mostly db stats and db user management from within Plesk. I'll give it a try.
  3. R

    Question Upgrade postgres

    @IgorG, what would happen if I installed a newer version that the ones currently supported by Plesk? As far as I can see, Plesk does not use PostgreSQL for any of it's own data, so is the worst that would happen is that the connection info in the database overview would be wrong?
  4. R

    PHP error.log: failed to notify status to systemd

    I'm also getting this error every 10 seconds in the FPM-PHP log. This is the place in the PHP source code it originates from. This may not be a Plesk-specific issue, but I cannot find anything about it anywhere else on the web. Is anyone able to provide more input on this?
Back
Top