• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Advanced Monitoring

TomBoB

Silver Pleskian
upgraded a second server from 17.8 to Obsidian. CentOS Linux 7.7.1908 Plesk Obsidian Version 18.0.19

Advanced Monitoring only displays

{"message":"Invalid username or password"}

EDIT
can replicate that when I open Grafana and go "open application"
 
Last edited:
Have you tried to fix it with

# plesk repair installation

?
 
yes did that, didn't help. Looking through the log files it complained about too many login attempts so left it for the night.

When testing in the morning after, it worked.
 
Hi,

can't open Advanced Monitoring two, for some time it hangs with the same error as above : {"message":"Invalid username or password"}
plesk repair installation did not solve the problem on my Debian 8. (Plesk is up to date)

var/log/grafana/grafana.log full of
"t=2020-04-27T12:00:26+0200 lvl=eror msg="Invalid username or password" logger=context error="Too many consecutive incorrect login attempts for user. Login for user temporarily blocked"

what I've tried :

-> restart grafana server
-> clone grafana.db in case it was corrupted
-> reset admin password via grafana-cli, based on the client_secret found in "grafana.ini" with no luck (then revert it to the old one directly in the database)

Any idea ?

Thanks
 
Back
Top