Search results

Yup! Same here! Upgrading "Advanced Monitoring" (and then Grafana Server to 8.0.3) did the trick, beside a minor hickup about some json not being installed, fixed by the ad-hoc "Fix installation" button. ... but I'm quite positive that the Advanced Monitoring extension upgrade wasn't offered...

It's in good company with Forwarded to devs - Let's Encrypt wildcard certificates are not issued for domain aliases and probably many others. Apparently sometimes "forwarded to devs" means "won't fix any time soon". What I find particularly frustrating is the canned answer "check the change...

@Auladig you might consider adding your voice to the above mentioned new issue tracker report...

@Rasp Done! TTL set for specific records does not propagate to DigitalOcean DNS

Username: Sergio Manzi TITLE TTL set for specific records does not propagate to DigitalOcean DNS PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian Version 18.0.36 CentOS Linux 7.9.2009 DigitalOcean DNS Version 1.3.1-116 PROBLEM DESCRIPTION TTL set for specific records does...

To all having problems (no data displayed...) after upgrading to grafana server 8.0.x: I'm quite convinced that this is the wrong thread for the issue and the correct one is Forwarded to devs - Advanced Monitoring extension not working with grafana 8.0.0-1 Please make your voice heard there...

Still not working here with Grafana Server Version 8.0.3 (commit: cae5c5e46b, branch: HEAD) and Grafana Extension 1.2.3-233 (even though it says that EXTPLESK-2710 is solved), and again downgrading to grafana-7.5.7-1 makes things work. As above, I'm working under CentOS Linux 7.9.2009, Plesk...

@Auladig I can confirm the same issue you are reporting (TTL set for specific records does not propagate to DigitalOcean), but apparently that's not what the OP issue was (and hence it seems "our" issue is not solved by EXTPLESK-1677 at all...). ALL records propagate to DigitalOcean with the...

Thanks @Nextgen-Networks My confusion comes from the fact that the OP of this issue was citing upgrading to grafana-7.4.0-1 as the triggering event, while in the "other issue" everything is working with grafana-7.5.7-1 ...

I'm confused: is this issue the same as Advanced Monitoring extension not working with grafana 8.0.0-1 ?

I can confirm this issue too (under Centos 7, Plesk 18.0.36) Temporarily fixed with: yum downgrade grafana-7.5.7-1 yum install yum-plugin-versionlock yum versionlock grafana-7*

Almost ten months passed, yet another update for the extension has been released, and yet no sign of this issue having been addressed: is it too much asking at least for an answer to why (apparently) this is not being taken into consideration? Edit: ... and BTW this is not even listed in the...

Thanks, will surely do as soon as 18.0.28 will be available.

User name: Sergio Manzi TITLE Plesk panel home page title not updated when switching from other context PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian Version 18.0.26 - CentOS Linux 7.8.2003 PROBLEM DESCRIPTION The home page title (in the browser tab) is not...

Thank-you very much, @mizar !

Hello everybody, Some days ago I have upgraded from Plesk Onyx to Obsidian (Version 18.0.26 under CentOS Linux 7.8 ). I have auto-update turned off (I prefer to be in control...) and today I was offered my first update since upgrading, but there is something fishy which I would like to check...

Could it be that this is related to this (Let's Encrypt wildcard certificates are not issued for domain aliases)?

Great, thank-you! Then, maybe, there is still hope to see this fixed...

I've recently updated from Onyx to Obsidian (nice!). I had a slight hope that this bug would be resolved in Obsidian, but unhappily it is not. The issue is open since August of the past year and I'm really starting wondering if there is any will from the Plesk part to have this fixed. I...

Thank you! Can you please publish what the URL should be, so that we can go to it manually by pasting it in the browser address bar?