• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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. V

    Forwarded to devs Grafana extension database rights too broad and cannot load unsigned backend plugin

    Ah, so I must have previously updated Grafana from the grafana repo. Thanks for linking to a quick and easy fix!
  2. V

    Forwarded to devs Grafana extension database rights too broad and cannot load unsigned backend plugin

    Ok, thanks IgorG, for updating the thread with an explanation from the developer. And lastly, how about the logged error about the missing folder /etc/grafana/provisioning/plugins?
  3. V

    Forwarded to devs Grafana extension database rights too broad and cannot load unsigned backend plugin

    And how about the file permissions for /var/lib/grafana/grafana.db, can these be safely changed to -rw-r----- ?
  4. V

    Forwarded to devs WordPress Toolkit - Updating website with different WP_CONTENT_URL shows incorrect warning

    Note that it's also impossible to Secure the option "Configure security keys" in the WordPress Toolkit when the WP_CONTENT_URL configuration constant is defined. Although this is probably a different issue, its cause might be related.
  5. V

    Forwarded to devs WordPress Toolkit - Updating website with different WP_CONTENT_URL shows incorrect warning

    Username: Visnet TITLE WordPress Toolkit - Updating website with different WP_CONTENT_URL shows incorrect warning PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian 18.0.33.0 CentOS 7.9.2009 x86_64 PROBLEM DESCRIPTION When updating a WordPress website that has the...
  6. V

    Forwarded to devs Grafana extension database rights too broad and cannot load unsigned backend plugin

    Username: Visnet TITLE Grafana extension database rights too broad and cannot load unsigned backend plugin PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian 18.0.33.0 CentOS 7.9.2009 x86_64 PROBLEM DESCRIPTION After having updated Grafana from Plesk's Grafana repo...
  7. V

    PHP 7.4 compatibility issue with Wordpress Toolkit

    Sorry, this is not useful as your answer is irrelevant. You are referring to checking for possible PHP 7.4 incompatibilities in websites, but the PHP warning discussed in this topic is coming from a component bundled with the WordPress Toolkit extension. As you can see in my repy I have already...
  8. V

    Forwarded to devs WordPress Toolkit - PHP warning - Deprecated: implode(): Passing glue string after array is deprecated.

    Interestingly enough, the version of WP-CLI bundled with the WordPress Toolkit extension is at version 1.4.0 (released Oct 17, 2017): # cat /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wp-cli/VERSION 1.4.0 Although at the moment of writing this, the current stable version of...
  9. V

    PHP 7.4 compatibility issue with Wordpress Toolkit

    Bug report posted in WordPress Toolkit - PHP warning - Deprecated: implode(): Passing glue string after array is deprecated.
  10. V

    Forwarded to devs WordPress Toolkit - PHP warning - Deprecated: implode(): Passing glue string after array is deprecated.

    Username: Visnet TITLE WordPress Toolkit - PHP warning - Deprecated: implode(): Passing glue string after array is deprecated. PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian 18.0.31.1 CentOS 7.9.2009 x86_64 PROBLEM DESCRIPTION Using PHP 7.4.12 as the primary PHP version...
  11. V

    PHP 7.4 compatibility issue with Wordpress Toolkit

    Same error. Over 850 occurrences in less than 2 months. Plesk Obsidian 18.0.31.0 CentOS 7.8.2003 x86_64 WordPress Toolkit version: 5.1.1-4424 Where to submit this as a bug?
  12. V

    Issue Plesk panel says update available, CLI says server already has the latest version

    That seemed to have done the trick, thank you, Hextrator! I hope I won't need this every time I want to update Plesk to the latest version...
  13. V

    Issue Plesk panel says update available, CLI says server already has the latest version

    # plesk installer list-all --- prod_id release_id (description) (tiers) --- plesk PLESK_18_0_28 (Plesk Obsidian 18.0.28) (development,testing,release,stable,current) plesk PLESK_18_0_27 (Plesk Obsidian 18.0.27)...
  14. V

    Issue Plesk panel says update available, CLI says server already has the latest version

    Same issue with Plesk Obsidian 18.0.28 Update 2 released yesterday on June 6th, 2020. Plesk does not auto-update nor can I update to the latest version through plesk installer update plesk. Why does Plesk Obsidian tell me I have the latest version, even though the autoinstaller log clearly...
  15. V

    Issue Plesk panel says update available, CLI says server already has the latest version

    This was not necessary for Plesk Onyx 17.8.x, I don't see why it would be necessary for Plesk Obsidian to allow incoming connections to this port if I prefer to use the CLI for updates. Also, from the logs it is clear that 18.0.28 is actually detected on the remote source, so I doesn't look...
  16. V

    Issue Plesk panel says update available, CLI says server already has the latest version

    I have purposefully closed port 8447 because of security reasons. Plesk panel seems to see the available update, though:
  17. V

    Issue Plesk panel says update available, CLI says server already has the latest version

    Note, after trying to install the update with plesk installer update plesk, I found the file /var/log/plesk/install/autoinstaller3.log to contain: [2020-06-28 20:28:47.473472] Release PLESK_18_0_28 is actual [2020-06-28 20:28:47.473555] Release PLESK_18_0_28 is minor upgrade (stay on current...
  18. V

    Issue Plesk panel says update available, CLI says server already has the latest version

    Currently running Plesk Obsidian 18.0.27.1, I noticed Plesk panel mentioning the newer 18.0.28, which I found to be released on June 23, 2020. However, if I try to update Plesk using plesk installer update plesk or plesk installer install-panel-updates, the installer says: You already have the...
  19. V

    Issue Server backup with important issues incorrectly marked as "minor issues", no notification sent

    Posted in Reports subforum here > Server backup with important issues incorrectly marked as "minor issues", no notification sent This topic can be closed or deleted.
  20. V

    Forwarded to devs Server backup with important issues incorrectly marked as "minor issues", no notification sent

    User name: Visnet TITLE Server backup with important issues incorrectly marked as "minor issues", no notification sent PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian 18.0.27.1 CentOS 7.8.2003 x86_64 MariaDB 10.3.23 PROBLEM DESCRIPTION Dear Plesk team, I am performing a...
Back
Top