Version 1.4.0 includes comprehensive security measures:
- β API key authentication required
- β Path traversal attacks blocked
- β All inputs validated
- β Security headers enabled
- β CORS restricted
- β Dependencies updated
- β Error messages sanitized
Your API key is like a password - keep it private!
Docker β Container icon β Logs β Look for:
Generated temporary key: xxxxx
openssl rand -base64 32Add to container's API_KEY environment variable.
- Never share your API key
- Don't expose port 8889 to internet - Local network only
- Use VPN for remote access
- Update container regularly
- Check logs periodically
"401 Unauthorized"
- API key missing or wrong
- Check Docker logs for key
Lost API Key
- Check Docker logs first
- Or: Stop β Clear
API_KEYβ Start β New key in logs
Do NOT open public GitHub issues!
Email maintainer directly or create private security advisory on GitHub.
- API key saved securely
-
FLASK_DEBUGis false - Not exposed to internet
- Container updated
- Logs monitored
For more details, see CHANGELOG.md