CRITICAL: Incorrect credentials given

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Post Reply
callcollin
Posts: 1
Joined: Wed Jul 23, 2025 10:40 am

CRITICAL: Incorrect credentials given

Post by callcollin »

Hello,

I am working with some Nagios XI servers and I have multiple hosts throwing "CRITICAL: Incorrect credentials given" errors on mainly McAfee and RMF related services. I checked/update the community token and made sure it matched. Also reset the services but still getting these errors.

I am new to Nagios so any help would be greatly appreciated. Someone else set this up prior and is no longer with the company.

Thanks
User avatar
lgute
Posts: 419
Joined: Mon Apr 06, 2020 2:49 pm

Re: CRITICAL: Incorrect credentials given

Post by lgute »

Hi @callcollin,

Thanks for reaching out.

How are these service checks on the affected hosts setup? You mention community token, so I'm guessing the checks may be setup using NCPA agents.

If you navigate to the Monitoring tab for one of the affected service check...
  1. Navigate to Configure | Core Config Manager
  2. Click on Services on the CCM Object Summary
  3. Click on the Config Name next to the name of one of the affected service checks
  4. Click on the Run Check Command button
  5. In the modal (popup window), click on the Run Check Command button
This will run the service check and output the complete command, with arguments, that is getting executed. It should look something like this, if the check is an NCPA check.
NCPAServiceCheckCCM.png
If you can provide the command that is being executed (redacted as necessary), that will give us a starting point.
You do not have the required permissions to view the files attached to this post.
Please let us know if you have any other questions or concerns.

-Laura
jsimon
Posts: 343
Joined: Wed Aug 23, 2023 11:27 am

Re: CRITICAL: Incorrect credentials given

Post by jsimon »

@callcollin,

Please be advised there is a known issue with special characters in NCPA tokens currently in XI, which could be affecting you depending on your token. This issue has been tagged with #1975 and has been addressed, so please keep an eye on the changelog in future releases for a fix.
Post Reply