Nagios Support Forum

Hello all,
after configuring SSL/TLS for the WEB interface the menus are no longer in error and the TOKEN is valid, I can now restart logstash or elasticsearch from the web interface.


All my worries are solved except sending email via an authenticated SMTP server

Hello all,
after configuring SSL/TLS for the WEB interface the menus are no longer in error and the TOKEN is valid, I can now restart logstash or elasticsearch from the web interface.

All my worries are solved except sending email via an authenticated SMTP server

ssunga wrote: ↑Mon Aug 12, 2024 12:10 pm some logging info would be good here

Hello, can you tell me which logs you want?

After doing a bit of digging into this, I've got an idea. For right now I'd like you to go into your user profile (click your user name in the upper right hand corner), and click generate new api key. Let's see if that resolves your problem. If not, go to the status pages you mentioned, hit the f12...

I reinstalled nagios log server on fresh centos 9 stream without any security profile installed and just minimal install and still the same problem. in : admin -> NCPA : NCPA active check listener : Could not authenticate. Invalid token given. NCPA Passive check Sender : Could not authenticate. Inva...

I was able to resolve the error in configure -> per instance by disabling the sudoers options that had been applied by the ANSSI BP intermediary security profile:
require tty
use_pty

the errors in admin -> system status and monitor backend are still present

how can i debug the tokens used by logstash and elasticsearch in order to investigate. the monitor backen (ncpa) page also indicates ncpa active and passive with the error "could not authenticate : invalid token given" however when i open the NCPA interface and connect with the NCPA API TO...

post to delete

Hello everyone, to begin with after a complete installation from a centos 9 machine, I observe errors in some menus: OS : CentOS Stram 9 - 5.14.0-480.el9 x86_64 Nagios log server version : 2024R1.1 ------------------------------------------------------------------------------------------------------...