Same problem for me to. The configuration file is like below, now. If I click on v6 from v5 it works but not the other way around. And the links always go to /v5, but if v5 is the default what's the point? I think that's the problem, instead of taking into account the config for the base they are explicitly passed in the links. The config [http] [http.cookies] [[http.listen]] port = 443 cert = '/opt/ssl-local/fullchain.pem' key = '/opt/ssl-local/privkey.pem' [http.mounts] '/v6' = '../../@xen-orchestra/web/dist/' '/' = '../xo-web/dist/' # List of proxied URLs (HTTP & WebSockets). [http.proxies] '/v5/api' = 'ws://localhost:9000/api' '/v5/api/updater' = 'ws://localhost:9001' '/v5/rest' = 'http://localhost:9000/rest' [redis] [remoteOptions] [plugins] The problem with /v5 [image: 1765705545615-b97eb845-a70b-43fb-8f7b-2ece31de7b4e-image.png]

For completeness sake. Confirming that the fix also works in my second lab as well.

@probain No worries, im still learning/improving my ansible/terraform skills aswell

Hi, That's because our doc isn't fully up to date with the new naming (even XO in the app itself). See this recap: [image: Schema-new-wording-backup-2.png] More details in here: https://xen-orchestra.com/blog/xen-orchestra-5-83/#backup-nomenclature

@florent It was working before, this is likely something that has been broken when the handling of snapshots has been moved from VMs to VDIs. We need to fix this.

@probain Noted in backlog

Question/suggestion to @julien-f and @florent

@probain As @olivierlambert said, Redis is used to story very little data, and we are already thinking about migrating away from it. We would like to use a simpler solution that would not require users to manage it like an SQLite database. For the time being, we will likely keep Redis as long as it's available in open source distributions like Debian but we are keeping an eye on it

@julien-f I can confirm that the fix worked! Snapshots are back and working. I am impressed at how quick you managed to fix it too. Thanks!