Skip to main content
All CollectionsInspectorsN-Central
N-Central | N-Central failing with a 401 error
N-Central | N-Central failing with a 401 error

If your N-Able N-Central inspector is failing with a 401 you can follow the below and that should bring the system back online

Updated over 8 months ago

Problem: If your N-Able N-Central inspector is failing with a 401 you can follow the below and that should bring the system back online

Steps to Resolution

  1. Change the Liongard service account password in N-Central

  2. Then regenerate the Liongard service accounts' API key

  3. Add the new API key into Liongard for the N-Central parent inspector

  4. Run N-Central parent inspector using Debug and Clear cache option

    1. Inspectors | How to run in "debug" and clear cache | Liongard Support Portal

  5. This should allow the system to land completed once more

Outcome: The inspector should start landing completed and no longer failing with a 401 error

Alternatives: If the 401 error still persists please reach out to support!

Did this answer your question?