|Nope - it is almost certainly a configuration issue. If monit was reloaded, then it is likely that your Monit CLI uses different monit configuration file then your monit daemon. |
To get the configuration file the CLI is using, run monit with debug options:
monit -vtI | grep "Control file"
You can see the path which is used by monit daemon in the GUI by clicking on the "running" link - the path to the configuration file is in the "Controlfile" field:
On 1 Feb 2017, at 17:14, Mohamed Sadok Ben Jazia <address@hidden> wrote:
Yes i did a monit reload, the new password is working well on the web panel.
However, it's not working on the CLI.
It seems like a bug on monit ?
On 1 February 2017 at 16:43, Martin Pala <address@hidden> wrote:
did you reload monit after the configuration was changed?:
If not, monit daemon is still using original credentials, whereas the CLI tries to login with new credentials.
On 1 Feb 2017, at 14:06, Mohamed Sadok Ben Jazia <address@hidden> wrote:
I used monit to monitor processes on debian.
I use this configuration that works
set httpd port 2812 and
use address 0.0.0.0
Then i needed to change the basic authentification password, i can use the new password in the admin web panel, but when i try monit tasks, "monit unmonitor all" for example, i get the following error:
You are <b>not</b> authorized to access <i>monit</i>. Either you supplied the wrong credentials (e.g. bad password), or your browser doesn't understand how to supply the credentials required
Any idea how to deal with this.