• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Search results

  1. F

    Forwarded to devs No graphs in monitoring after grafana-8.3.6-1.x86_64 update

    Thanx! Installed nginx and all websites kept running smoothly under Apache. Strange that Apache is not supported anymore by Grafana. But the install of nginx was unavoidable over time :-)
  2. F

    Forwarded to devs No graphs in monitoring after grafana-8.3.6-1.x86_64 update

    It was not installed on my Plesk server on delivery. I could install it, but the websites I moved there were built without nginx as well. Installing nginx could maybe make a mess of it all. So I'd still like to make Grafana work without nginx.
  3. F

    Forwarded to devs No graphs in monitoring after grafana-8.3.6-1.x86_64 update

    Hi Maarten, On github I stumbled on some comments about ProxyPreserveHost (Unable to Create/Save Dashboard after v8.3.5 Update · Issue #45117 · grafana/grafana) Could that have something to do with this. Because I don't have nginx (or ipv6), only apache. If this can resolve the problem, clould...
  4. F

    Forwarded to devs No graphs in monitoring after grafana-8.3.6-1.x86_64 update

    Thanks for the suggestion. But it does not solve the problem. I reported it to your Plesk partner.
  5. F

    Forwarded to devs No graphs in monitoring after grafana-8.3.6-1.x86_64 update

    BTW: I have another plesk server with comparable settings (Ubuntu 20.04.4 LTS). But not updated to 18.0.42 and with no reinstall of monitoring or grafana. grafana_plesk.inc is the same. This I see in the grafana.log. This is the complete log. The issue was only after the update Grafana was...
  6. F

    Forwarded to devs No graphs in monitoring after grafana-8.3.6-1.x86_64 update

    I just did a reinstall of monitoring and grafana. After that no change in grafana_plesk.inc: location /modules/grafana/service/ { proxy_set_header Host $http_host; proxy_pass http://127.0.0.1:3030/; rewrite ^/modules/grafana/service/login$...
  7. F

    Forwarded to devs No graphs in monitoring after grafana-8.3.6-1.x86_64 update

    Hi Igor, I installed Plesk 18.0.42 just now on my Ubuntu 20.04.4 LTS. But I see no improvement on the monitoring. I still get "origin not allowed". As I mentioned before, the proxy_set_header is set. Grafana version is 8.3.6. The extension Grafana says version 1.3.2-286. Have I missed something?
  8. F

    Resolved Wrong cpu subscription monitoring

    After update: https://talk.plesk.com/threads/no-graphs-in-monitoring-after-grafana-8-3-6-1-x86_64-update.364086/#post-905365
  9. F

    Forwarded to devs No graphs in monitoring after grafana-8.3.6-1.x86_64 update

    I have the same problem, but the suggested quick fix does not help me. The proxy_set_header is already set. Reloading or restarting grafana does not help either. Maybe another way to solve this?
  10. F

    Resolved Wrong cpu subscription monitoring

    None of the current reporters is allowed to file an official report. So someone else has to do that?
  11. F

    Resolved Wrong cpu subscription monitoring

    Having the same problem on Ubuntu 20.04.4 LTS Product Plesk Obsidian Versie 18.0.41 Update #1
  12. F

    Resolved Backup problem after upgrade to Obsidian 18.0.40

    Can you give us an update? Backups of my critical websites are well overdue.
Back
Top