NTA troubleshooting

This document provides troubleshooting guidance for common issues when deploying and running Invicti Network Traffic Analyzer (NTA).

Authorization failures

If the NTA is unable to authorize with Invicti Platform (receiving HTTP 401 responses), it will automatically retry the authorization attempt. After 3 failed retries, the NTA will gracefully shut down with an error message indicating the authorization failure.

Common causes of authorization failures:

• Invalid or expired registration token
• Incorrect Invicti Platform credentials (email or license key)
• Network connectivity issues preventing access to Invicti Platform
• Token not saved after generation (the Save step was skipped during token generation)

To resolve:

1. Verify your registration token is valid and was saved in the Invicti Platform (check Discovery > Configuration > API sources)

2. Confirm that your Invicti Platform email and license key are correct

3. Ensure network connectivity from your deployment environment to Invicti Platform

4. Generate a new registration token if needed and update your deployment configuration

5. Check the NTA logs for specific error messages:

   For Kubernetes deployments:

   kubectl logs <reconstructor-pod-name> -n <your-namespace>

   For Docker deployments:

   docker logs <container-name>

Pod/Container status issues

If NTA components are in CrashLoopBackOff or Error states, check the logs for specific error messages and verify:

• Registration token is valid and properly configured
• Network policies allow outbound connections to Invicti Platform
• Resource limits are appropriate for your traffic volume
• All required environment variables are set correctly

Check pod status (Kubernetes):

kubectl get pods -n <your-namespace>

Check container status (Docker):

docker ps -a

Network connectivity issues

If the NTA cannot reach Invicti Platform:

1. Verify firewall rules allow outbound HTTPS connections

2. Check proxy configurations if using a corporate proxy

3. Ensure DNS resolution works for Invicti Platform endpoints

4. Test connectivity from your deployment environment:

   curl -I https://platform.invicti.com

No APIs appearing in API Inventory

If NTA is running but APIs are not appearing in your API Inventory:

1. Verify traffic is actually flowing through the monitored interfaces/endpoints
2. Check that traffic matches the capture criteria (HTTP methods, status codes)
3. Confirm the NTA has successfully authorized (check logs)
4. Wait a few minutes - API reconstruction and sync may take time
5. Check the reconstructor logs for processing errors

Need help?

Invicti Support team is ready to provide you with technical help. Go to Help Center