getting 404 shortly after starting with aw-qt

Not sure if I should post here or in the main activitywatch repo.
I'm running into an issue where if I run aw-qt, and then migrate to 127.0.0.1 I immediately get a 404 message from rocket.

## steps to reproduce
1. clone activity watch, pull submodules, cd into the top-level repo
2. create and activate the .venv
3. run `make build`
4. cd to `.venv/bin` run `./aw-qt`
5. navigate to `127.0.0.1:5600` or `local:5600`

the output from the process is complaining about a None response:

```
[2023-03-13 14:35:36][WARN][_]: Response was `None`.
[2023-03-13 14:35:36][WARN][_]: No 404 catcher registered. Using Rocket default.
[2023-03-13 14:35:37][WARN][_]: Response was `None`.
[2023-03-13 14:35:37][WARN][_]: No 404 catcher registered. Using Rocket default.
2023-03-13 14:37:59 [INFO ]: Became AFK (aw_watcher_afk.afk:97)
```

it's also worth noting that when I run with `cargo run --bin aw-server` the webui works as expected.