• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved Grafana service returns "403 forbidden" errors

QWeb Ric

Basic Pleskian
One of our client servers suffered a filesystem corruption so we've set up a new server, installed Plesk, and then restored everything from Plesk backup to bring back the websites and various configurations. This mostly worked but we're having a few teething issues with this server now.

One of which is that Advanced Monitoring just isn't working. The pages were displaying oAuth.login errors before, and restarting the service had no effect. I've managed to partly resolve by running plesk bin extension --install grafana and then restarting the service via the Plesk interface, so now the graphs are loaded into the pages, but they all just show a red exclamation icon in the top left corner and the hover text of this says "metric request error". Running systemctl status grafana-server results in these lines: tsdb.HandleRequest() error rpc error: code = Unknown desc = invalid status code. status: 403 Forbidden.

Any ideas please?

Plesk Obsidian 18.0.21 on CentOS 7.
 
Ah!

I've reinstalled Grafana and I'd restarted the service multiple times, but I hadn't thought to try reinstalling Advanced Monitoring. This seems to have done the trick, thanks!
 
Back
Top