Pius Troubleshooting - Common Issues and Fixes

No CIDR results

Cause: Phase 1 plugins found no RIR handles, or handles returned no CIDRs.

Solutions:

1. Try alternate spellings of the organization name: --org "Acme Corporation" vs --org "Acme Corp"
2. Isolate the whois plugin to check if handles are found: --plugins whois
3. Verify the organization has direct RIR allocations (some organizations use cloud provider IP space exclusively)

No domain results

Cause: Missing domain hint, or API keys not set.

Solutions:

1. Add --domain to unlock crt-sh and DNS plugins
2. Set API keys: APOLLO_API_KEY, SECURITYTRAILS_API_KEY, or VIEWDNS_API_KEY
3. Run pius list to confirm which plugins are registered

See Configuration for the full environment variable reference.

APNIC or AFRINIC results are stale

Cause: RPSL database cache is within its 24-hour TTL.

Solution:

rm ~/.pius/cache/*.rpsl
pius run --org "Acme Corp"

Rate limiting from GitHub

Cause: GITHUB_TOKEN not set. Unauthenticated requests are limited to 60/hr.

Solution:

export GITHUB_TOKEN="ghp_..."
pius run --org "Acme Corp"

Slow CIDR discovery

Cause: Multiple RDAP requests per handle across multiple registries.

Solutions:

• Reduce concurrency: --concurrency 3
• Restrict to specific registries if you know the organization's region:

# Only query ARIN (faster for US-based organizations)
pius run --org "Acme Corp" --plugins whois,arin

Plugin is not running

Cause: The plugin's Accepts() check is returning false, usually due to a missing API key or input hint.

Solution: Check that the required environment variable is set and the needed input (--org, --domain, or --asn) is provided. Run pius list to see all registered plugins.

Related pages

• Configuration - Environment variables and cache settings
• FAQ - Answers to common questions
• Plugins - Plugin requirements and data sources