Skip to main content

Installation Errors

Error Message:
Cause: The virtual environment was not created during installation or was deleted.Solution:
1

Recreate the virtual environment

2

Activate the environment

3

Reinstall dependencies

Always activate the virtual environment before running AutoPentestX to ensure all dependencies are available.
Error Message:
Cause: Python dependencies were not installed or the virtual environment is not activated.Solution:
Never install packages globally with sudo pip. Always use the virtual environment to avoid system-wide conflicts.
Error Message:
Cause: Package lists are outdated or repository issues.Solution:
1

Update package lists

2

Upgrade system packages

3

Install packages manually

4

Rerun installation script


Runtime Errors

Error Message:
Cause: Target IP/domain cannot be resolved or is unreachable.Solution:
1

Verify network connectivity

2

Check DNS resolution (for domains)

3

Verify target format

Make sure you’re using a valid IP address or domain:
  • Valid: 192.168.1.100, example.com, 10.0.0.1
  • Invalid: 192.168.1.1000, example .com, http://example.com
4

Check firewall rules

Ensure you have network access to the target and that no firewall is blocking your scans.
Symptoms:
  • Scan completes but shows 0 open ports
  • All ports appear filtered or closed
  • PDF report has minimal information
Possible Causes:
  1. Target has no open ports (unlikely)
  2. Firewall is blocking scan traffic
  3. Insufficient permissions (no sudo)
  4. Network restrictions
Solutions:
Start with a quick scan on localhost (127.0.0.1) to verify AutoPentestX is working correctly before scanning remote targets.
Error Message:
Cause: PDF generation libraries are corrupted or missing dependencies.Solution:
1

Reinstall PDF libraries

2

Install system dependencies

3

Verify installation

4

Check reports directory

Even if report generation fails, scan data is still saved to the SQLite database in database/autopentestx.db.
Error Message:
Solutions:
When pressing Ctrl+C during a scan:Expected Behavior:
The scan will gracefully terminate and mark the status as “interrupted” in the database.If AutoPentestX hangs:
1

Force terminate

Press Ctrl+C multiple times or use:
2

Check for zombie processes

Some subprocesses (Nmap, Nikto, SQLMap) may continue running even after terminating AutoPentestX. Always verify they’re stopped.

Tool-Specific Errors

Error Message:
Solution:
Nmap is required for all network scanning operations. AutoPentestX cannot function without it.
Error Message:
Solution:
Workaround:
Error Message:
Solution:
Skip SQL injection testing:
Warning Message:
Solution:
1

Install Metasploit

2

Verify installation

Workaround:
Metasploit is optional. AutoPentestX can perform reconnaissance and vulnerability scanning without it.

Performance Issues

Symptoms: Scan runs for 30+ minutesSolutions:
Use --skip-web --skip-exploit for quick reconnaissance, then run a full scan later if needed.

Getting Help

If your issue is not listed here:
  1. Check the logs: ls -lh logs/ and examine recent log files
  2. Review scan database: sqlite3 database/autopentestx.db "SELECT * FROM scans ORDER BY id DESC LIMIT 5;"
  3. Test components individually: Run Nmap, Nikto, and SQLMap manually to isolate the issue
  4. Consult other troubleshooting pages:

Still Need Help?

Open an issue on GitHub with your error logs and system information