Helmer

I found what is causing the issue, it's a Cloudflare protection thing. So it has nothing to do with Discvault. I thought I solved it, since my external hosted test container was able to just fix it. Do you have Discord...? We could have a chat there (around 20:00 CET) to see how to solve it. That is faster then just going back and forth on a forum. The link to join the Discord is on the website.

I think i've found the issue. It's not related to DiscVault or Movievault, but a Coudflare issue. I think i've solved it, could you please try again?

Thanks, let me dive into this. I'll get back to you when I've found the cause.

Could you check the logs for me, in the Admin menu (the Audit tab) and then select the Plugins log and open the audit details and share the JSON (by pressing Copy JSON). You can share it here (or through a DM), please remove your IP address if you want.

26.2.57 is good. The DiscVault Image set to auto is good. What about the reset connection button for the plugin?

And if you select the beta version in the drop-down, which version do you see there? Interesting that you see 26.2.55, since the latest version (in PROD is 26.2.57). Could you try and set the Always recreate Stack to true and share the logs of the Discvault-26 container (after restarting it and after it ends with DiscVault launcher is ready) And for the plugin, can you click ' Reset connection'. That should initiate a new security handshake and let me know if you pressed that and I''ll take a look at the backend if I see something in the logs'.

This has also been resolved: https://github.com/helmerzNL/DiscVault/issues/111

This issue also has been resolved: https://github.com/helmerzNL/DiscVault/issues/108

This issue has been resolved: https://github.com/helmerzNL/DiscVault/issues/112

You should be running (at least) this version, which should work. If you have deployed the app with the DiscVault launcher, just restart the launcher should update the app to the version mentioned above. If it doesn't work, please let me know and I can help you troubleshoot.

Hi! Thanks a lot for testing stuff out. I'll need to do some checks and then respond to all the questions. One quick question, which build are you running? You should be able to see it in the Profile -> About page (should be something like 26.x.x) and are you running the beta (v26-beta) or stable (v26) built? The beta currently has a lot of new features (check the website for the list of new features), you should be able to move between the two without an issue. Plugin MovieVault26 errors out with "Health: connection error - HTTP 200" i had to disable it. neither version 1.5.0 nor 1.5.3 works for me. what do you mean by that? The Movievault plugin is the metadata plugin I developed, which seems to give an issue on your end. There have been some auth-sync changed being made, I don't see any requests coming in from an unknown/new DiscVault instance. I'll do some testing to see what's going on if there is a new DiscVault instance knocking on the door, maybe I did not push out the new stuff the pROD version yet.

Oke, if you btw have issues scanning certain (types) of movies, let me know. it's quiet difficult to get access to 'public' API's that allow for barcode readers, so i have something built in works for almost all my movies. But specific (older) DVD's for the Dutch market are not always recognized :-( That's why i also build an metadata search engine that movie data flows back into, so it only has be be contributed once. Not sure if it works with a barcode reader? It works with the camera of my laptop and the one on my iPHone, but the native iPHone app works best (and the fastest). Let me know if you want to test that one, and i'll send you the testflight linm If you could could reach your internal FQDN through the browser on your phone, then the app would also work. It just connects to your FQDN and you authenticate with your Passkey. If you could DM me your Apple ID then I can add you to TestFlight.

What did you fill out here (when you are configuring the app). This is how you should fill them out.

Btw, if you would be able to have your own service accessible from the outside (through a VPN etc). I'm currently in the process of developing an iOS/iPadOS native app. If you have an iPhone, I could add you to Testflight and you would be able to test it out. Although it's a bit rough on the edge still.

To be honest. What i use for my internal services is NPM Proxy Manager (on my Unraid), for which i have registered a *.local.domain.tld (which only resolves through my internal dns) and that way you can create local (FQDN) domainnames (so no need to access service on IP:port, but a clear https://discvault.local.domain.tld. That works great with Passkeys as well no access from the outside and not resolvable (since port 443 exposed to the outside world) and DNS is not giving any hosts away. But for this you do need to have a real domainname, that's it.

Were you able to get it up and running?

I've updated the FAQ with an article explaining why it's required and the wizard should now give you an understandable error if you don't have a fqdn setup.

Please use a fqdn, so for example RP_ID : disc.domain.com and RP_ORIGINS: https://disc.domain.com. That's a requirement for Passkeys, since they are domain-bound. You can obviously use an internal domainname, as long as you use one. I'll add some error-handling to the wizard, it can be a bit unclear what the issue is.

No problem :-) You did use the DiscVault 26 from the Community App Store to get it working, right? and what did you enter at the RP_ORIGINS and RP_ID fields?

btw, you were not running the 'legacy' version before? Or is this the first install/try?

I've tried Safari on my mac/iPhone/iPad and i've used Edge on Windows and all work fine. Let me see if i can reproduce it. I need to adjust the instructions above, since the new DiscVault 26 version has a little bit of a different approach then the legacy one. Did you use the

👋 Welcome to the official support thread for DiscVault — a self-hosted collection manager for your physical 4K UHD, Blu-ray, and DVD library. This thread now covers the current DiscVault 26 release. If you're still running the older single-container Legacy release, support for that continues here too — just let us know which version you're on when you post. 🎬 What is DiscVault?DiscVault lets you catalog, browse, and manage your physical disc collection from any device — desktop or mobile. Scan a barcode, pull in cover art and metadata, organize box sets and collections, and keep a personal watchlist and watch history. Everything stays self-hosted and under your own control. ✨ What's new in DiscVault 26DiscVault 26 is a from-the-ground-up foundation for the project. It keeps the same self-hosted, collector-first focus, but modernizes the stack: New desktop-first library with poster, list, and detail views Richer movie and container detail pages (backdrops, posters, videos, box-set contents) PostgreSQL-backed data model, replacing the old SQLite-based Legacy storage A plugin runtime for metadata sources, receivers, import sources, and digital media sources RBAC, invite-only login, role simulation, and audit views in the admin area API access and MCP-ready endpoints for AI assistant integration A guided migration assistant that walks you from an existing Legacy install into 26 ⚠️ Important for Unraid users: DiscVault 26 runs on the DiscVault LauncherDiscVault Legacy shipped as a single all-in-one container. DiscVault 26 is a small stack — PostgreSQL, an API service, and a worker — so on Unraid, the DiscVault 26 app installs and runs through the DiscVault Launcher out of the box. You don't need to set this up separately: installing "DiscVault" from Community Apps gives you the Launcher container, and it takes care of the rest. The Launcher is a small deployment manager that: Talks to the Docker socket to spin up and manage the v26 stack (Postgres + API + worker) — or the Legacy single container, if you select that channel instead Proxies everything through one stable WebUI port, so your existing port (e.g. 6080) doesn't change Handles secrets generation (Postgres password, JWT secret) and keeps them stable across updates Watches for new DiscVault image versions and republishes the matching Launcher tag automatically Launcher repo: https://github.com/helmerzNL/DiscVault-Launcher Recommended appdata paths when setting it up: /mnt/user/appdata/discvault existing data (Legacy SQLite DB, media) /mnt/user/appdata/discvault-postgres PostgreSQL data for the v26 stack /mnt/user/appdata/discvault-launcher Launcher config and generated secrets After install, open the WebUI — if you have existing Legacy data, it will prompt you to run the migration assistant at /api/next/migration. If you only want to keep running the old single-container Legacy release, the Launcher handles that too — it manages Legacy installs (legacy channel) as well as the v26 stack, just running the one container in that case instead of the full stack. 🐳 Imagesghcr.io/helmerzNL/DiscVault:v26 — current DiscVault 26 release ghcr.io/helmerzNL/DiscVault:legacy — old single-container Legacy release Unraid Community Apps template repo: https://github.com/helmerzNL/unraid-templates 🔄 Migrating an existing Legacy installThe built-in migration wizard walks you through it end to end: Confirm your current install — the wizard detects your existing DiscVault data Authenticate with your existing passkey and review what will be migrated Confirm and run the migration, with progress shown until DiscVault 26 is ready Take a backup before you start. Keep your existing persistent data and volume mappings in place until the migration completes successfully. 🔗 LinksWebsite: https://discvault.eu Source / GitHub: https://github.com/helmerzNL/DiscVault DiscVault Launcher: https://github.com/helmerzNL/DiscVault-Launcher Discord: https://discord.gg/jSUfV7PT Report an issue: https://github.com/helmerzNL/DiscVault/issues 🙋 Posting for supportTo help diagnose issues quickly, please include: Whether you're on the v26, v26-beta, or legacy channel Your Unraid version Container logs for DiscVault and the Launcher Steps to reproduce, and what you expected to happen instead Thanks for using DiscVault — looking forward to your feedback on 26! 🙌

It booted from the stock v7 image, but after i copied the /config folder over it booted, but gave an bzmodules checksum error and i needed to press Enter to reboot. Then it did not recognize the USB stick and went straight to the BIOS, but after another reboot It booted again, with the same errorl After a 2nd try, the first time i did not let the stock image boot until it was finished. With the first try I let the stock image boot, until there was a sign in prompt on the cmdline. After which I shutdown the server and restored the /config folder and booted the server again, after which my server was up and running again. Thanks @JorgeB!

Not sure what happened, but this morning I started the upgrade from RC2 to the 7.0 version. But after an hour or so the machine still wasn't finished, so i connected a screen to it and noticed that it was unable to boot. It didnt recognize the USB stick anymore as a bootable device. I was able to read the USB stick (in anotherzbnas-diagnostics-20250110-1051.zip computer) and I have attached the diagnostics here:zbnas-diagnostics-20250110-1051.zip Any ideas what to do?

I’m happy to be a tester as well.