Find solutions to common problems you might encounter when using Strix.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/usestrix/strix/llms.txt
Use this file to discover all available pages before exploring further.
Docker Issues
Docker is not running
Symptom: Error message “Docker is not available” or “Docker daemon is not running” Solutions:-
Start Docker Desktop
- On macOS/Windows: Launch Docker Desktop from Applications
- On Linux:
sudo systemctl start docker
-
Verify Docker is running
Should show running containers or empty list, not an error.
-
Check Docker permissions (Linux)
-
Reinstall Docker if necessary
- Download from docker.com
- Follow installation instructions for your OS
Port already in use
Symptom: Error “port 48080 or 48081 already in use” Solutions:-
Find and stop the process using the port
-
Stop previous Strix containers
-
Clean up all stopped containers
Container fails to start
Symptom: Container starts then immediately exits Solutions:-
Check Docker logs
-
Ensure sufficient resources
- Docker Desktop → Settings → Resources
- Allocate at least 4 GB RAM
- Ensure 10 GB+ free disk space
-
Pull latest image
-
Remove corrupted images
Image pull fails
Symptom: Cannot download Strix Docker image Solutions:-
Check internet connectivity
-
Configure Docker proxy (if behind firewall)
- Docker Desktop → Settings → Resources → Proxies
- Add your proxy configuration
-
Use alternative registry mirror
-
Manual pull with retry
LLM Connection Issues
Invalid API key
Symptom: “Authentication failed” or “Invalid API key” Solutions:-
Verify API key is correct
Should print your key, not empty.
-
Check for extra spaces or quotes
-
Regenerate API key
- Go to your LLM provider’s dashboard
- Create new API key
- Update environment variable
-
Check key permissions
- Ensure API key has necessary permissions
- Some providers require specific scopes enabled
Model not found
Symptom: “Model ‘X’ not found” or “Unsupported model” Solutions:-
Use correct model format
- Check supported models See LLM Providers for complete list.
-
Verify model access
- Some models require approval or waitlist access
- Check your provider’s dashboard
-
Use alternative model
Rate limiting
Symptom: “Rate limit exceeded” or 429 errors Solutions:-
Wait before retrying
- Most providers: 60 seconds
- Check provider’s rate limit documentation
-
Use different API key
- Create separate key with independent limits
- Use organization-level keys for higher limits
-
Upgrade API plan
- Higher tiers usually have increased rate limits
- Consider provider’s team/enterprise plans
-
Use slower scan mode
-
Switch to different provider
Connection timeout
Symptom: “Connection timeout” or “Request timed out” Solutions:-
Check internet connectivity
-
Increase timeout
-
Configure proxy if needed
-
Use different API base URL
Quota exceeded
Symptom: “Quota exceeded” or “Insufficient credits” Solutions:-
Check account balance
- Log into provider dashboard
- Verify billing information is current
-
Add credits or upgrade plan
- Add payment method
- Purchase additional credits
-
Use Strix Router for free credit
Installation Issues
Python version too old
Symptom: “Python 3.12+ required” or import errors Solutions:-
Check Python version
-
Install Python 3.12+
-
Use pyenv for version management
pip install fails
Symptom: Errors duringpip install strix-agent
Solutions:
-
Upgrade pip
-
Use pipx (recommended)
-
Install with verbose output
Review errors for specific missing dependencies.
-
Install from source
Command not found
Symptom:strix: command not found after installation
Solutions:
-
Add pip/pipx to PATH
-
Use python -m
-
Verify installation location
Scan Issues
Scan hangs or freezes
Symptom: Scan appears stuck with no progress Solutions:-
Check LLM API status
- Visit provider status page
- Look for service disruptions
-
Enable debug logging
-
Reduce scan complexity
-
Check system resources
No vulnerabilities found
Symptom: Scan completes but reports no findings Possible causes:- Application is secure - This is good news!
-
Insufficient testing depth
-
Missing authentication
-
Scope too narrow
Too many false positives
Symptom: Scan reports vulnerabilities that don’t exist Solutions:-
Review findings carefully
- Check the proof-of-concept
- Verify reproduction steps
- Strix validates most findings, but confirm manually
-
Use higher quality models
-
Provide more context
-
Report false positives
- Help improve Strix by reporting issues
- GitHub Issues
Scan crashes
Symptom: Strix exits unexpectedly with error Solutions:-
Check error message
- Read the full traceback
- Look for specific error codes
-
Update to latest version
-
Clear Docker cache
-
Report the crash
- Include full error traceback
- GitHub Issues
Configuration Issues
Environment variables not persisting
Symptom: Variables work in terminal but not after restart Solutions:-
Add to shell configuration
-
Use Strix config file
Strix saves configuration to
~/.strix/cli-config.jsonautomatically. -
Use .env file
Cannot access target URL
Symptom: “Cannot connect to target” or “Target unreachable” Solutions:-
Verify URL is accessible
-
Check for localhost/internal IPs
-
Configure Docker network
-
Disable SSL verification (not recommended)
Performance Issues
Scans are very slow
Solutions:-
Use faster LLM models
-
Enable prompt caching
-
Use quick scan mode
-
Allocate more Docker resources
- Docker Desktop → Settings → Resources
- Increase CPU and RAM allocation
High memory usage
Solutions:-
Limit concurrent agents
-
Use smaller context windows
-
Close other applications
- Free up system RAM
- Docker requires significant resources
Getting Help
If you’re still experiencing issues:-
Search existing issues
- GitHub Issues
- Someone may have encountered the same problem
-
Join Discord community
- discord.gg/strix-ai
- Get real-time help from community
-
Create detailed bug report
- Include system information
- Provide full error traceback
- List steps to reproduce
- See Contributing Guide
- Check documentation