Resolved Plesk Obsidian -Version 18.0.50 - Monitoring Grafana / Server Error

[weareimpulse]

Server operating system version

Ubuntu 20.04.5 LTS

Plesk version and microupdate number

18.0.50

Hi, after upgrading PLESK to 18.0.50, the Monitoring tool (Grafana) is down.

Grafana / Server Error
Sadly something went wrong
login.OAuthLogin(NewTransportWithCode)

Check the Grafana server logs for the detailed error message.

Does anyone have a workaround/fix, please?

 

[Peter Debik]

If you believe you have found a bug, please report it here: Reports

 

[Redsector]

Same bug here with 2 servers. I can't report it as I have just registered. In the log mentioned above there is:

t=2023-01-31T11:22:14-0500 lvl=eror msg=login.OAuthLogin(NewTransportWithCode) logger=context userId=0 orgId=0 uname= error="oauth2: cannot fetch token: 500 Internal Server Error\nResponse: {\"error\":\"unknown_error\",\"error_description\":\"It was not possible to parse your key, reason: \",\"message\":\"It was not possible to parse your key, reason: \"}"

and after some time it appears as:
t=2023-01-31T14:30:12-0500 lvl=eror msg="invalid username or password" logger=context error="too many consecutive incorrect login attempts for user - login for user temporarily blocked"

 

[shou80]

Hello,

got the same problem on Ubuntu 22.04 , on 2 fresh new installs....
I just spent 2 hours trying to get this on its feets with no luck...

 

[scencula]

Same problem with CentOS 7 after 18.0.50 update

 

[learning_curve]

This has been reported as a bug:

Update to Plesk Obsidian 18.0.50 breaks Grafana and the monitoring extension

Username: TITLE Update to 18.0.50 breaks Grafana PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE AlmaLinux 8.7 Plesk Obsidian Version 18.0.50 PROBLEM DESCRIPTION When you upgrade Plesk to 18.0.50, the Grafana extension gives an error: 500 TypeError Mezzio\Router\Route::__construct()...

talk.plesk.com

 

[AYamshanov]

JFYI, the bug is fixed with the Grafana extension v1.3.5.