# Upgrading This page lists what changes on the first start after an upgrade, and what to do where something needs doing. ## Upgrading to library databases in the data folder - **The beets library databases move out of the music folders.** Each music folder's `.beets_library.db` moves from the root of that folder to `beets-libraries` next to Soulbeet's database (`/data/beets-libraries/music/Person1/.beets_library.db` for `/music/Person1`), on the first start, or for a folder that is not there then, on its first import, delete or replace. A database on a network share made imports fail with "database is locked"; keep `/data` on a local disk, and your music can stay on the share. Back up `beets-libraries` with the database from now on. If you run `beet` yourself, point `-l` at the new path and pass `-d` with the music folder (see [Library databases](beets.md#library-databases)). - **Tracks whose file is gone leave the beets libraries.** Earlier versions left a track in the library of a Discovery profile folder for each discovery track that was removed, expired or kept. Each start now drops, from the library of every music folder and of its Discovery profile folders, the tracks whose file is gone, and touches no file. A library none of whose tracks has its file there, as on a share that is not mounted, is left as it is (see [Tracks whose file is gone](beets.md#tracks-whose-file-is-gone)). ## Upgrading to roles and folder roots The release that adds admin roles changes a few things on the first start: - **Everyone is signed out once.** Sessions from earlier versions are no longer accepted. Sign in again. - **The shipped `admin` password only signs in to choose a new one.** If the seeded `admin` account still has the password `admin`, its next sign-in asks for a new password, and until one is chosen the account can do nothing else. Another admin can also set one in Settings > Users. - **The seeded `admin` account is the only admin.** If it was deleted, the oldest account becomes admin instead. Every other account, Navidrome accounts included, becomes a plain user and no longer sees user management, the slskd settings, Security Checks or the folder administration. Sign in as `admin` and click **Make admin** next to your own account in Settings > Users. Before you upgrade, check that you can sign in as `admin`. If you no longer know the admin password and no other admin exists, nothing in the app gives the role back: stop Soulbeet, then run `sqlite3 soulbeet.db "UPDATE users SET role = 'admin' WHERE username = 'yourname'"` on the database file (in the `./data` volume of the [Quick Start](../README.md#quick-start)). The Soulbeet image has no `sqlite3`; if the host has none either, copy the file to a machine that has it while Soulbeet is stopped, run the command there and copy it back before starting Soulbeet. - **A generated secret key replaces the built-in one and any short one.** An install that ran without `SECRET_KEY` used a key built into Soulbeet, and earlier example files set short placeholders such as `a_secret_key` or `change-me-in-production`. Anyone who knows such a key can sign themselves in as any user, so Soulbeet no longer signs with the built-in key or with any `SECRET_KEY` under 32 bytes: on the first start it generates a key and stores it in `secret.key` next to the database. Everyone is signed out once. Stored Navidrome passwords are stored again under the new key on that start, so nobody has to enter theirs again. Back up `secret.key` with the database from now on, and remove a short `SECRET_KEY` (Security Checks lists it until you do). An install that sets a `SECRET_KEY` of at least 32 bytes keeps it. - **`NAVIDROME_MUSIC_PATH` names Soulbeet's own path now.** Earlier versions read it as the path Navidrome uses for its music. It now names where Soulbeet sees the root of Navidrome's default library. If you set it before, change it to the path inside the Soulbeet container (for example `/music/common` when Navidrome's library is `/media/music/common` and Soulbeet mounts `/media/music` at `/music`), or remove it. While it names no folder Soulbeet can see, the startup log and Settings > Library > Deletion Checks say so, and no song of that library is deleted or replaced. - **Behind a reverse proxy, the live Downloads panel needs the public name.** The download updates socket now opens only from Soulbeet's own page: the page's address must match the address the request was sent to, or `PUBLIC_URL`. A proxy must pass the public name in `Host` (nginx: `proxy_set_header Host $host;`) or `X-Forwarded-Host`, or `PUBLIC_URL` must be set to it. Otherwise the Downloads panel stays empty and the log says "Refused a download updates socket" with both addresses. - **Navidrome's ReportRealPath is no longer used.** Deletion and the rating sync find files from Navidrome's library paths. You can leave the player setting as it is; a "ReportRealPath not enabled" status is cleared on the first start. - **Usernames ignore letter case.** Accounts whose names differ only in letter case (`bob` and `Bob`) sign in only with their exact name, and other spellings such as `BOB` are refused. The startup log lists them; an admin deletes the ones that are not used in Settings > Users. - **Signing out ends the session on the server**, so a copied cookie stops working too. Your other devices stay signed in. - **Registration is closed.** `REGISTRATION` now defaults to `navidrome` with `NAVIDROME_URL` set and to `admin` without it. Set `REGISTRATION=open` to keep the old behaviour. - **Folder roots.** The upgrade approves the parent directory of each existing admin folder, so an admin folder at `/music/main` approves `/music`. It never approves `/`, so a top-level admin folder such as `/music` approves nothing: add `/music` as a root and tick **Shared** on that folder before other users add folders inside it. - **Folder conflicts.** Existing folders that are outside every root, or that equal, contain or sit inside another user's folder, are listed under Folder Conflicts in Settings > Library. They keep working and can still be renamed in place, but a move to another path has to pass the folder rules. To solve one, tick **Shared** on one of the folders, or delete a folder entry there (its files stay on disk). ## Upgrading to the MCP server The release that adds the MCP server has its own upgrade notes in [mcp.md](mcp.md#upgrading).