---
since: 1.0.6
---

# Troubleshooting

## `DjangoPlay repository not detected`

Run the command from inside the DjangoPlay Git repository:

```bash
cd /path/to/djangoplay
dplay http
```

The detector uses:

```bash
git rev-parse --show-toplevel
```

and additionally checks that the repository path contains `djangoplay`.

## `Virtual environment not active`

Activate the project's virtual environment before running the CLI.

```bash
source .venv/bin/activate
```

Then:

```bash
dplay system doctor
```

## Missing configuration

Create:

```text
~/.dplay/config.yaml
```

The CLI raises an error if this file is absent.

## Redis unavailable

Check:

```bash
redis-cli ping
```

The expected response is:

```text
PONG
```

## PostgreSQL unavailable

The doctor command checks TCP connectivity to:

```text
127.0.0.1:5432
```

This is a reachability check, not an authentication check.

## Celery unavailable

The doctor command checks whether the `celery` executable is available on
`PATH`.

## Celery does not become ready

The startup flow waits up to 20 seconds for a process matching:

```text
celery.*paystream
```

If the process is not detected, startup continues with a warning.

Inspect Celery separately before treating the Django server as healthy.

## Static collection fails

The CLI invokes:

```bash
python manage.py collectstatic --noinput --clear
```

from the `webapp` directory.

Run the command manually to inspect the host application's full error.

## Browser does not open

The CLI uses Python's `webbrowser` module. The server itself can still start
if browser launching is unsuccessful.