# NSClient++ : MISSING TOKEN error

**URL:** <https://community.icinga.com/t/nsclient-missing-token-error/15437>\
**Category:** Icinga 2\
**Tags:** nsclient\
**Created:** [May 12, 2026, 7:26am UTC](https://community.icinga.com/t/nsclient-missing-token-error/15437 "2026-05-12T07:26:28Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gaetan](https://community.icinga.com/letter_avatar_proxy/v4/letter/g/b77776/32.png) [@Gaetan](https://community.icinga.com/u/Gaetan)\
**Post date:** [May 12, 2026, 7:26am UTC](https://community.icinga.com/t/nsclient-missing-token-error/15437/1 "2026-05-12T07:26:28Z")

</div>

Hello,

I have a setup consisting of several windows server machines monitored by an Icinga2 instance installed on a Debian 13 server. Each machine has an Icinga2 agent installed (v2.16), as well as NSClient++ (with versions 9 and 10). On the Icinga2 side of things, I call the nscp api like this: [https://icinga.com/docs/icinga-2/snapshot/doc/06-distributed-monitoring/#distributed-monitoring-windows-nscp-check-api](https://icinga.com/docs/icinga-2/snapshot/doc/06-distributed-monitoring/#distributed-monitoring-windows-nscp-check-api)

The setup works well, but I added a new machine and installed NSClient++ v11.8 on it and I am getting 403 errors in Icinga2. Looking in nsclient.log I am getting these errors every time I try to run a service that uses NSClient. Icinga2 basic services work fine. I have not altered the nsclient.ini file.

[![Image](https://community.icinga.com/uploads/default/original/2X/8/8c83c90c1d2607304f4746177231d1f93a380d8c.png)](https://private-user-images.githubusercontent.com/235039249/558751719-734953da-46f9-45cd-9215-96884602d219.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Nzg1NzA3OTEsIm5iZiI6MTc3ODU3MDQ5MSwicGF0aCI6Ii8yMzUwMzkyNDkvNTU4NzUxNzE5LTczNDk1M2RhLTQ2ZjktNDVjZC05MjE1LTk2ODg0NjAyZDIxOS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwNTEyJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDUxMlQwNzIxMzFaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0xNmY5OGY1NTAyZDRmNTk5MmNkNGExOGRmM2Y5YjkzMTAxMDZiMDAzMjBlMjY5ZmFmYmE4YTlmMTQ3NTc2ZTAzJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZyZXNwb25zZS1jb250ZW50LXR5cGU9aW1hZ2UlMkZwbmcifQ.pRkOEo7eQb3T4KNugZhBLJuiQyI_v-XYi0SyuQph91M)

Locally NSClient++ seems to run its own checks just fine:

 ![image](https://community.icinga.com/uploads/default/original/2X/f/f33f9dc0539a4a235fc2128ec74387191162caef.png)

I have pinpointed the exact NSClient++ version where this stops working as 0.11.6. The error occurs both on a fresh install of nscp and upon upgrading a previous version.

Icinga2 version: r2.16.0-1

Enabled features: api checker command icingadb influxdb mainlog notification

`icinga2 daemon -C` is green

Don’t hesitate if you need more details.

Thank you.

---

<div class="post-metadata">

**Author:** ![lorenz](https://community.icinga.com/user_avatar/community.icinga.com/lorenz/32/7666_2.png) [@lorenz](https://community.icinga.com/u/lorenz)\
**Post date:** [May 12, 2026, 9:02am UTC](https://community.icinga.com/t/nsclient-missing-token-error/15437/2 "2026-05-12T09:02:27Z")

</div>

It looks like there are [breaking changes in NSclient++](https://github.com/mickem/nscp/releases/tag/0.12.3).  
But I am not sure how to adapt to this.

---

<div class="post-metadata">

**Author:** ![Gaetan](https://community.icinga.com/letter_avatar_proxy/v4/letter/g/b77776/32.png) [@Gaetan](https://community.icinga.com/u/Gaetan)\
**Post date:** [May 12, 2026, 9:38am UTC](https://community.icinga.com/t/nsclient-missing-token-error/15437/3 "2026-05-12T09:38:33Z")

</div>

Thanks. Yes I can see that there is some mention of tokens:

 ![image](https://community.icinga.com/uploads/default/original/2X/8/8c5f9acbc723d73755431faabcf56390baef133b.png)  
I just don’t do anything myself with the tokens so I don’t really know what to change. I wonder if this is something to do with the nscp plugin for Icinga2 itself. I’d be curious to see if anyone has the same problem (I haven’t found anything online right now).

---

<div class="post-metadata">

**Author:** ![lorenz](https://community.icinga.com/user_avatar/community.icinga.com/lorenz/32/7666_2.png) [@lorenz](https://community.icinga.com/u/lorenz)\
**Post date:** [May 12, 2026, 9:57am UTC](https://community.icinga.com/t/nsclient-missing-token-error/15437/4 "2026-05-12T09:57:41Z")

</div>

This is the first time I am seeing this, but we commonly no longer deploy NSclient++ in our customer setup since it became stagnant a few years ago, so there is not a lot of data.

Thank you for reporting this. This might be a good starting point for people with the same issue.

---

<div class="post-metadata">

**Author:** ![apenning](https://community.icinga.com/user_avatar/community.icinga.com/apenning/32/7669_2.png) [@apenning](https://community.icinga.com/u/apenning)\
**Post date:** [May 12, 2026, 10:08am UTC](https://community.icinga.com/t/nsclient-missing-token-error/15437/5 "2026-05-12T10:08:14Z")

</div>

AFAIK, Icinga 2’s `check_nscp_api` does not make any use of tokens, but passes the password as an additional HTTP request header.

> <https://github.com/Icinga/icinga2/blob/f50f6ec88fbbb6bf86569ea0a89a4b5e8b51e47b/plugins/check_nscp_api.cpp#L373>

It was a bit hard for me to skim over the latest changelogs and pinpoint something specific, so I would guess reporting this to the nscp bug tracker would be a good idea.

---

<div class="post-metadata">

**Author:** ![Peer-Mario](https://community.icinga.com/letter_avatar_proxy/v4/letter/p/aeb1de/32.png) [@Peer-Mario](https://community.icinga.com/u/Peer-Mario)\
**Post date:** [May 18, 2026, 6:36am UTC](https://community.icinga.com/t/nsclient-missing-token-error/15437/6 "2026-05-18T06:36:23Z")

</div>

That’s why we use SNClient 🙂

---

<div class="post-metadata">

**Author:** ![lorenz](https://community.icinga.com/user_avatar/community.icinga.com/lorenz/32/7666_2.png) [@lorenz](https://community.icinga.com/u/lorenz)\
**Post date:** [May 18, 2026, 7:20am UTC](https://community.icinga.com/t/nsclient-missing-token-error/15437/7 "2026-05-18T07:20:06Z")

</div>

That would be [this one](https://omd.consol.de/docs/snclient/) and I would recommend to try this as a replacement.

---

<div class="post-metadata">

**Author:** ![Gaetan](https://community.icinga.com/letter_avatar_proxy/v4/letter/g/b77776/32.png) [@Gaetan](https://community.icinga.com/u/Gaetan)\
**Post date:** [May 18, 2026, 8:34am UTC](https://community.icinga.com/t/nsclient-missing-token-error/15437/8 "2026-05-18T08:34:49Z")

</div>

Thanks for the replies and suggestions. NSClient++ has since reportedly patched the issue in version 0.12.4. I haven’t had time to test it yet but I will report when I have.

---

<div class="post-metadata">

**Author:** ![Gaetan](https://community.icinga.com/letter_avatar_proxy/v4/letter/g/b77776/32.png) [@Gaetan](https://community.icinga.com/u/Gaetan)\
**Post date:** [May 26, 2026, 9:06am UTC](https://community.icinga.com/t/nsclient-missing-token-error/15437/9 "2026-05-26T09:06:03Z")

</div>

I have tested the newest version of NSClient++ and it works fine. Thanks everyone.
