vulncheck
6969d0c62e
VulnCheck - Open Source Vulnerability Management for Wazuh Features: - Vulnerability management with Wazuh integration - AI-powered CVE analysis (OpenAI, Anthropic, Google, DeepSeek, Ollama, Infomaniak) - SLA policy enforcement with automated email alerts - Automated patch verification via Wazuh Syscollector - Role-based access control (Admin, Editor, Readonly) - PDF/CSV reporting for compliance workflows - Full audit trail https://gitea.isuit.ch/vulncheck/vulncheck
3.1 KiB
Troubleshooting & Operation Guide
This guide provides solutions to common issues and a reference for essential operational commands.
Common Operations (Docker)
These commands assume you are in the project root directory.
Start/Stop Application
Start everything (detached mode):
docker compose up -d
Stop everything:
docker compose down
Updates & Rebuilds
Pull latest code and rebuild:
git pull origin main
docker compose up -d --build
Rebuild only one service (e.g., backend):
docker compose up -d --build backend
Logs & Monitoring
View live logs for all services:
docker compose logs -f
View logs for specific service:
docker compose logs -f backend
docker compose logs -f frontend
Database Maintenance
Access database console:
docker compose exec db psql -U vulnmanager -d vulnmanager
Run migrations manually:
docker compose exec backend alembic upgrade head
Troubleshooting Guide
1. "Database unreachable" or "Connection refused"
Symptoms: Backend crashes on startup, logs show OperationalError.
Solutions:
- Ensure the database container is running:
docker compose ps - Check if
POSTGRES_PASSWORDin.envmatches the one in the database. - Fix: If you changed the password in
.envafter the first run, you must delete the existing database volume to reset it (WARNING: Data loss):docker compose down -v docker compose up -d
2. Wazuh Synchronization Failed
Symptoms: "Wazuh API Error", "Authentication failed", or assets not appearing.
Solutions:
- Check Credentials: Verify API URL, Username, and Password in
Settings>Wazuh. - Self-Signed Certificates: If Wazuh uses a self-signed cert, ensure
Verify SSLis unchecked in Settings. - Network: Check if the backend container can reach the Wazuh manager.
docker compose exec backend curl -v -k https://<YOUR_WAZUH_IP>:55000
3. "Violations: 3" (Red Card in Dashboard)
Context: This was a legacy placeholder card. Status: It has been removed in the latest version. If you still see it, clear your browser cache or rebuild the frontend container.
4. Scheduler / Emails Not Sending
Symptoms: No emails on SLA breach, or scans not starting.
Solutions:
- Check Logs: Look for scheduler errors in backend logs:
docker compose logs -f backend | grep scheduler - SMTP: Go to
Settings->SMTPand use the "Test Connection" button. - Timezone: Ensure
TIMEZONEin.envis correct (Europe/Zurich, etc.) for correct scheduling.
5. Deployment Issues (Permission Denied)
Symptoms: EACCES or permission errors in Docker logs.
Solutions:
- Ensure scripts are executable:
chmod +x *.sh - Ensure Docker runs with sufficient privileges or as the correct user.
Support
For further assistance, please open an issue on Gitea or contact support: Email: support-vulncheck.sq9vd@passmail.net