Search results

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

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:

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 !=...

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

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 :(

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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