v2.0.0-preview-3 #2671
Replies: 5 comments 8 replies
|
Hi |
|
2026/07/25 14:54:41 [FATAL] server.database.migrateFrom is "database.db.old" but that file does not exist, and no SQLite database exists at server.database.path ("filebrowser.sqlite"). Check the migrateFrom path or restore your renamed legacy database backup. See the v2 migration guide: https://filebrowserquantum.com/en/docs/getting-started/v2/migration this is my docker compose: |
|
Hi @pbranly this is a good point, the issue is clear, I need to update it use the env variables that docker uses by default. You can work around this now by setting the migrate from path to the same default docker uses: The above should work if you renamed your database to that. I will update this to be smoother in the future by making the config convert tool understand this better. |
|
Hi |
|
Hi Nevertheless I still get a 500 error |
|
Ah thanks for the logs -- this is probably specific to the use of |
|
understood: noauth: truedoes not work anymore and had to deactivate |
|
it should work still, probably just a small thing missing which I will fix in another preview. |
|
I got errors in filebrowers when conducting the migration, using the migration script at: The migration config.yaml output had the following on lines 40 thru 48 respectively: The filebrowser quantum container produced the following logged output:
The config rewrite didn't properly configure the user permissions. I deleted the failed configuration options within the config.yaml file and continued the mirgration. The next issue is with the OIDC callback URI error with authentik. I initially had breaking callback errors with filebrowser. I had to troubleshoot to identify the issue was because the changes within the http of the new configuration yaml aren't being properly parsed and setup for the OIDC. You have to added the externalURL to my https callback URI for filebrowser under the http section, as well as add the the X-Forwarded-Proto, X-Forwarded-Host X-Forwarded-For under the trustedHeaders section as well.
After implementing those two changes I was able to get filebrowser to start and login successfully. My running filebrowser container logs are: Just an FYI that either the documentation for v2 may need to be updated for OIDC configuration. Also the parser logic like another user mentioned may need to be updated as well for both userdefaults and OIDC configuration logic. Hope this helps someone else if they are have an issue. |
|
thanks for the details on this. permissions should get remapped where userDefaults.permissions.create gets applied to each source This should be a simple fix as well as other small changes. I will keep you updated when thats ready in a few days. |
|
I noticed something about the user defaults. I thought the ones you set in the config would be 'locked' in the settings ui, and I remember that worked when trying it out some time while on development. Or not sure if something else changed and is intended since I saw in the logs a deprecation message rather than say that they will be used to lock them. Not related with the migration, but there's also an issue with the view tokens. Seems that they are restricted to only work in the current directory, and for example in markdown files it will block the loading of images if you have them into another dir (even if the directory where the image is, is a sibling of the md file). And that gets expired while I'm on preview, I left a video paused to continue watching it later with the browser tab in the background and when returning to continue watching it I needed to do a page refresh and seek manually where I was. It was a bit annoying since it happened various times :,) |
|
|
yeah, I also saw someone raised an issue related to the tokens but on shares (#2680) |
Uh oh!
There was an error while loading. Please reload this page.
What's Changed
Caution
This is a pre-beta preview of v2.0.0 and should be treated as a test build. Make sure you keep your existing configuration and files safe.
This version represents the most significant change to date. It requires both a database migration and config structural changes. See the migration guide for step-by-step upgrade instructions, About v2.0.0 for a full summary, and the config migration tool to convert legacy config.
ATTENTION: Consider enabling opt-in analytics in
settings > system & adminto help populate some of the deployment info data. Join the discussion on this release for support or issues you notice.Breaking Changes:
GET /api/rawandGET /public/api/rawdownload routes — use/api/resources/downloadinstead./share/…URL redirect to/public/share/…— use/public/share/…directly.sourcesearch api param (usesources), barescopepaths withoutsourceName:prefix, andglob/useGlobaliases (useuseWildcard).config.conditionals, source-levelindexingIntervalMinutes(indexing always uses adaptive scheduling), and deprecated rule fieldsfileNames/folderNames/ top-levelhidden— useconfig.ruleswithfileName,folderName, andignoreHiddenon rules.userDefaultsconfig formats (nested and flat) — use the config migration tool to convert before upgrading.PUT /api/usersmoved to the more appropriatePATCHmethod.serverconfig key moved tohttpconfig key. See HTTP settings.FILEBROWSER_DATABASEenvironment variable — useFILEBROWSER_DATABASE_PATHinstead. See Environment variables and Server settings./api/media/stream. See API reference.user set <username> --password [value]anduser promote <username>;set -u username,passwordis deprecated. See CLI reference.New Features:
settings > access managementviewpermission is automatically set to true unless explicitly set to false. See Access control overview.F4shortcut to refresh the current directory and metadata (Improve more the playback queue + metadata caching #2600).X-OC-Mtimeheader for clients that support it (add webdav X-OC-Mtime header support #2626). See WebDAV docs.COPYpreserves modification times only for files, is limitation we have with webdav.userDefaultsseeds SQLite on first run; only fields explicitly set in config stay locked in Settings → User defaults (other defaults remain editable)settings > user management > user defaults.settings > access management.FILEBROWSER_DATABASEis removed (startup fails if set). UseFILEBROWSER_DATABASE_PATH(defaultfilebrowser.sqlite) orserver.database.pathin config. See Environment variables and Server settings.user setwith--password(inline value, interactive prompt on TTY, or piped stdin);user promotefor admin grant without password reset. See CLI reference.Notes:
./filebrowser),setup,version, andset rulesyntax unchanged; see CLI docsuser.idhas been moved to a backend property and all frontend apis now query users by username. Swagger has been updated. See API reference./api/media/streamis audio/video only (range-based chunking). Non-media inline viewing usesGET /api/resources/view. Both endpoints use the sameviewTokenfrom file metadata. See API reference.This discussion was created from the release v2.0.0-preview-3.
All reactions