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

    Resolved Error E: Conflicting values set for option Signed-By regarding source http://autoinstall.plesk.com/PMM_1.0.0/

    Thank you for your answer. Could you mark the topic as resolved? Might help others, having the same problems.
  2. T

    Resolved Error E: Conflicting values set for option Signed-By regarding source http://autoinstall.plesk.com/PMM_1.0.0/

    Moving mv plesk-ext-site-import.list out of the the /etc/apt/sources.list.d/ directory, fixed the issue. I wonder how this can happen. In my opinion this is a bug in Plesk. :rolleyes:
  3. T

    Resolved Error E: Conflicting values set for option Signed-By regarding source http://autoinstall.plesk.com/PMM_1.0.0/

    This command does not work, because of the mentioned error. Synchronizing the Debian APT package index files... E: Conflicting values set for option Signed-By regarding source http://autoinstall.plesk.com/PMM_1.0.0/ focal: /etc/apt/keyrings/plesk-ext-panel-migrator.gpg !=...
  4. T

    Resolved Error E: Conflicting values set for option Signed-By regarding source http://autoinstall.plesk.com/PMM_1.0.0/

    Thank you for your help. I can not identify any duplicates on /etc/apt/sources.list.d focal-icinga.list imunify360.list imunify-rollout-bypass.list.disabled imunify-rollout.list imunify-rollout.list.save kcare.list kcare.list.save plesk-ext-docker.list plesk-ext-docker.list.save...
  5. T

    Resolved Error E: Conflicting values set for option Signed-By regarding source http://autoinstall.plesk.com/PMM_1.0.0/

    I thought I could fix the issue by updating Plesk to Version 18.0.67 Update #3. Unfortunately I can not open https://plesk.server.domain:8447, when I open Tools & Settings, "Updates" in Plesk :(
  6. T

    Resolved Error E: Conflicting values set for option Signed-By regarding source http://autoinstall.plesk.com/PMM_1.0.0/

    Hi all, since today I receive the following error message, when I run, for example, the command "apt list exim". As I did not modify anything on the server in the last days and no changes where applied as part of "unattended-upgrades", I am a bit clueless, where this error comes from and how...
  7. T

    Forwarded to devs Bug in 360 monitoring "status" panel

    Thanks for the update and confirming, that it is a bug on your side and that it's being worked on. :)
  8. T

    Forwarded to devs Bug in 360 monitoring "status" panel

    Hi, I am using plesk 360 monitoring. Together with this service I use the subdomain "status" to use a short overview, which can be used to view the uptime per day per domain. In this view I have found a bug in the details page of a monitored domain. I would be happy to report it somewhere...
    • theunknownstuntman
    • Thread
    • 360 monitoring cpcloud-4612 plesk 360 monitoring pps-16929
    • Replies: 4
    • Forum: Reports
  9. T

    Cron <psaadm@....> /opt/psa/admin/bin/php -dauto_prepend_file=sdk.php '/opt/psa/admin/plib/modules/wp-toolkit/scripts/maintenance.php' > /dev/null

    This issue has resolved itself without any doings on my side on all affected servers.
  10. T

    Resolved Grafana fails: Option '[alerting].enabled' cannot be true. Legacy Alerting is removed. It is no longer deployed, enhanced, or supported.

    With the help of the support I could fix this now. The solution was: - ssh to the affected server - remove or comment out the grafana repository in /etc/apt/sources.list - run the following commands: -- apt-get purge grafana -- plesk bin extension -u monitoring - login to Plesk admin panel...
  11. T

    Resolved Grafana fails: Option '[alerting].enabled' cannot be true. Legacy Alerting is removed. It is no longer deployed, enhanced, or supported.

    This Unable to access Advanced Monitoring in Plesk: Dashboard not found - Support Cases from Plesk Knowledge Base did not help either.
  12. T

    Resolved Grafana fails: Option '[alerting].enabled' cannot be true. Legacy Alerting is removed. It is no longer deployed, enhanced, or supported.

    In /var/log/grafana/grafana.log I can find the following errors. logger=renderer.manager t=2024-05-22T13:42:25.363741166+02:00 level=error msg="Failed to get renderer plugin sources" error="failed to open plugins path" logger=plugin.sources t=2024-05-22T13:42:25.367214559+02:00 level=error...
  13. T

    Resolved Grafana fails: Option '[alerting].enabled' cannot be true. Legacy Alerting is removed. It is no longer deployed, enhanced, or supported.

    Ok, I have now uninstalled grafana via apt, installed the extension via Plesk, commented out "[alerting].enabled", and installed the monitoring extension. When I now open Monitoring in Plesk I receive the message "Dashboard not found". Following this advice Issue - Dashboard Not Found and...
  14. T

    Resolved Grafana fails: Option '[alerting].enabled' cannot be true. Legacy Alerting is removed. It is no longer deployed, enhanced, or supported.

    I thought I need to install the Grafana extension on top of the grafana package (via apt) together with the monitoring extension in plesk. As far as I understand you, I do not need the grafana extension, when grafana was already installed via apt package manager or am I still confusing...
  15. T

    Resolved Grafana fails: Option '[alerting].enabled' cannot be true. Legacy Alerting is removed. It is no longer deployed, enhanced, or supported.

    Thank you @Kaspar@Plesk for your answer. I tried "enabled = false" before, and now also commented the section out. After I restarted Grafana, the service was running again. vim /etc/grafana/grafana.ini root@wiki:~# systemctl restart grafana-server.service root@wiki:~# systemctl status...
  16. T

    Resolved Grafana fails: Option '[alerting].enabled' cannot be true. Legacy Alerting is removed. It is no longer deployed, enhanced, or supported.

    As discussed here Question - Grafana update for cve-2023-6152 still missing in https://autoinstall.plesk.com/grafana/deb I decided to install the still missing grafana update manually to version 10.4.2 via deb https://packages.grafana.com/oss/deb stable main At first everything worked fine...
  17. T

    Question Grafana update for cve-2023-6152 still missing in https://autoinstall.plesk.com/grafana/deb

    Hi, when may I expect the delivery of the patched grafana versions to 10.3.3, 10.2.4, 10.1.7, 10.0.11 and 9.5.16. https://grafana.com/security/security-advisories/cve-2023-6152/ These are still missing in Index of /grafana/deb
  18. T

    Question Should I upgrade from Ubuntu 18.0.4?

    You should upgrade to Ubuntu 20.0x or better Ubuntu 22.0x (LTS). Ubuntu 18.0x (LTS) is also end-of-life. https://endoflife.software/operating-systems/linux/ubuntu Taking a server backup or downloading a server snapshot before doing so, is the minimum. If that causes any problems, depends on...
  19. T

    Resolved Smtp Smuggling advisory

    For Ubuntu "focal" is "postfix (3.4.13-0ubuntu1.3)" available, which includes the final fix for CVE-2023-51764: "smtpd_forbid_bare_newline = yes" http://changelogs.ubuntu.com/changelogs/pool/main/p/postfix/postfix_3.4.13-0ubuntu1.3/changelog
  20. T

    Resolved Smtp Smuggling advisory

    Thank you very much for answer. Meanwhile I have applied the fix which is applicable for all Postfix versions. I am curious, when the postfix 3.5.x package is available. In Ubuntu 20.04.6 LTS only postfix 3.4.13 is included. The above mentioned fix is not fully adressing the vulnerability...
Back
Top