Troubleshooting
Diagnosing a failed or partial installation.
Troubleshooting DefectDojo
Restart DefectDojo:
cd ~/apps/scansuite/defectdojo && sudo docker compose down -t 0
sudo docker compose up -dUpdate the DefectDojo admin password:
cd ~/apps/scansuite/defectdojo && ./dojo-passwordIn exceptional cases, reset the DefectDojo database. This command clears the DefectDojo database and restarts it from scratch:
~/apps/scansuite/defectdojo/reset-dojoResetting the database destroys every finding and product stored in DefectDojo. It also generates a new admin user, so you will need to fetch a new API key and update the ScanSuite settings.
After the reset, wait a few minutes and check for the new password:
cd ~/apps/scansuite/defectdojo && ./dojo-passwordFor more details refer to the official DefectDojo repository and documentation.
Troubleshooting ScanSuite
Restart ScanSuite:
cd ~/apps/scansuite && ./start-scansuiteTo check container logs for errors, change into ~/apps/scansuite and run the command for the service you are investigating. The architecture page explains what each one does.
docker compose logs web
docker compose logs worker
docker compose logs worker_admin
docker compose logs celery_beatThe application log is written to the host:
cat /var/tmp/scansuite.logIf containers fail to start at all, restart the Docker service itself:
sudo service docker restartLast reviewed 2026-08-15