Deployment

Troubleshooting

Diagnosing a failed or partial installation.

Troubleshooting DefectDojo

Restart DefectDojo:

bash
cd ~/apps/scansuite/defectdojo && sudo docker compose down -t 0
sudo docker compose up -d

Update the DefectDojo admin password:

Shell
cd ~/apps/scansuite/defectdojo && ./dojo-password

In exceptional cases, reset the DefectDojo database. This command clears the DefectDojo database and restarts it from scratch:

Shell
~/apps/scansuite/defectdojo/reset-dojo

Resetting 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:

Shell
cd ~/apps/scansuite/defectdojo && ./dojo-password

For more details refer to the official DefectDojo repository and documentation.

Troubleshooting ScanSuite

Restart ScanSuite:

Shell
cd ~/apps/scansuite && ./start-scansuite

To 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.

bash
docker compose logs web
docker compose logs worker
docker compose logs worker_admin
docker compose logs celery_beat

The application log is written to the host:

Shell
cat /var/tmp/scansuite.log

If containers fail to start at all, restart the Docker service itself:

Shell
sudo service docker restart

Last reviewed 2026-08-15