diff --git a/.github/resources/setup-wizard.png b/.github/resources/setup-wizard.png new file mode 100644 index 00000000..6dd86978 Binary files /dev/null and b/.github/resources/setup-wizard.png differ diff --git a/docs/getting-started/quick-start.md b/docs/getting-started/quick-start.md index bd79db92..485d9212 100644 --- a/docs/getting-started/quick-start.md +++ b/docs/getting-started/quick-start.md @@ -83,6 +83,10 @@ docker ps -f name=romm Open `http://:8080` in a browser. On first start, you'll be redirected to the **Setup Wizard**. Set an admin username and password (the first user created always gets the Admin role), then log in. +### Setup Wizard + +![A screenshot of the RomM Setup Wizard](.github/resources/setup-wizard.png "A screenshot of the RomM Setup Wizard") + ## Next steps - Populate the library by [scanning the mounted ROMs](first-scan.md) diff --git a/docs/troubleshooting/index.md b/docs/troubleshooting/index.md index 90691d73..b4836d4a 100644 --- a/docs/troubleshooting/index.md +++ b/docs/troubleshooting/index.md @@ -11,6 +11,13 @@ description: Diagnose common issues by symptom - Database connection errors → verify `DB_HOST`/`DB_PASSWD` match your DB container, and that the DB has finished initialising (first run takes longer than you'd think). - "Page not found" on first load → wait, because initial migrations and resource seeding take a minute. +## No Setup Wizard + +- If you do not see the setup wizard upon first connecting, and instead see a login screen, first check to see if the version number in the bottom right is `0.0.0`. If it is, RomM is functional and accessible, but not configured correctly, + and you will not be able to login, no matter what username and password you try. +- Ensure that you have modified `path/to/library`,`path/to/assets`, and `path/to/configs` in your `docker-compose.yml` so that they point to directories on the host. +- `/romm/library`, `/romm/assets`, and `/romm/config` should remain unchanged, as these refer to directories inside the docker container itself. + ## Login issues - Getting 403s → [Authentication Troubleshooting](authentication.md)