XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Some dashboard loading issues with v6

    Scheduled Pinned Locked Moved Solved Xen Orchestra
    27 Posts 4 Posters 1.5k Views 5 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • MathieuRAM Offline
      MathieuRA Vates šŸŖ XO Team @acebmxer
      last edited by

      @acebmxer Thanks.
      So, no issue to compute the dashboard.

      In your log, I see unexpected 401 responses code.

      Could you try /rest/v0/schedules and let me know the result? (and any XO-server errors that occur)

      acebmxerA 1 Reply Last reply Reply Quote 0
      • acebmxerA Offline
        acebmxer @MathieuRA
        last edited by

        @MathieuRA

        [
  "/rest/v0/schedules/8cf0dcb7-2122-41c6-8a2c-5c150308b292",
  "/rest/v0/schedules/22ce7eb8-ea62-4cbd-8e9b-646f99b6896c",
  "/rest/v0/schedules/f3504435-9e2b-4e43-a4f4-2f70aa51aa30",
  "/rest/v0/schedules/d5f4478e-4bba-4679-be5b-375f7c9aeb09",
  "/rest/v0/schedules/77e3804e-2180-458a-969b-d08f44504c3a",
  "/rest/v0/schedules/aa8ee2fb-6587-4a5f-a7c7-f292f563b43c",
  "/rest/v0/schedules/70c6cfc3-baa6-4c8f-804b-ba273b14267d",
  "/rest/v0/schedules/da426cb4-9bc2-46bf-a5c6-268bb67b80ad",
  "/rest/v0/schedules/b4fa328a-856a-4e00-8e14-7353d45a79e1",
  "/rest/v0/schedules/5906f9f7-ca8f-4623-954c-744f0615fb55",
  "/rest/v0/schedules/3059d28e-eaf1-449f-a0d1-fece3712df0c",
  "/rest/v0/schedules/14b6af3b-5d2f-4bd2-9d80-440c1d773e2a",
  "/rest/v0/schedules/f45a8928-bf4b-4d36-bfb2-3d96735ef8fd"
]

        āÆ journalctl -u xo-server -f -n 50
May 21 07:20:45 xo-ce xo-server[8974]:   }
May 21 07:20:45 xo-ce xo-server[8974]: }
May 21 07:20:45 xo-ce xo-server[8974]: 2026-05-21T07:20:45.705Z xo:xapi:xapi-disks INFO export through vhd
May 21 07:20:47 xo-ce xo-server[8974]: 2026-05-21T07:20:47.589Z xo:xapi:vdi WARN invalid HTTP header in response body {
May 21 07:20:47 xo-ce xo-server[8974]:   body: 'HTTP/1.1 500 Internal Error\r\n' +
May 21 07:20:47 xo-ce xo-server[8974]:     'content-length: 318\r\n' +
May 21 07:20:47 xo-ce xo-server[8974]:     'content-type: text/html\r\n' +
May 21 07:20:47 xo-ce xo-server[8974]:     'connection: close\r\n' +
May 21 07:20:47 xo-ce xo-server[8974]:     'cache-control: no-cache, no-store\r\n' +
May 21 07:20:47 xo-ce xo-server[8974]:     '\r\n' +
May 21 07:20:47 xo-ce xo-server[8974]:     '<html><body><h1>HTTP 500 internal server error</h1>An unexpected error occurred; please wait a while and try again. If the problem persists, please contact your support representative.<h1> Additional information </h1>VDI_INCOMPATIBLE_TYPE: [ OpaqueRef:fdeb8877-741a-d753-988f-34f20417f451; CBT metadata ]</body></html>'
May 21 07:20:47 xo-ce xo-server[8974]: }
May 21 07:20:47 xo-ce xo-server[8974]: 2026-05-21T07:20:47.598Z xo:xapi:xapi-disks WARN can't compute delta OpaqueRef:e17293bd-788e-1391-4567-4a3b9f2be433 from OpaqueRef:fdeb8877-741a-d753-988f-34f20417f451, fallBack to a full {
May 21 07:20:47 xo-ce xo-server[8974]:   error: Error: invalid HTTP header in response body
May 21 07:20:47 xo-ce xo-server[8974]:       at checkVdiExport (file:///opt/xen-orchestra/@xen-orchestra/xapi/vdi.mjs:37:19)
May 21 07:20:47 xo-ce xo-server[8974]:       at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
May 21 07:20:47 xo-ce xo-server[8974]:       at async Xapi.exportContent (file:///opt/xen-orchestra/@xen-orchestra/xapi/vdi.mjs:261:5)
May 21 07:20:47 xo-ce xo-server[8974]:       at async #getExportStream (file:///opt/xen-orchestra/@xen-orchestra/xapi/disks/XapiVhdStreamSource.mjs:123:20)
May 21 07:20:47 xo-ce xo-server[8974]:       at async XapiVhdStreamSource.init (file:///opt/xen-orchestra/@xen-orchestra/xapi/disks/XapiVhdStreamSource.mjs:135:23)
May 21 07:20:47 xo-ce xo-server[8974]:       at async #openExportStream (file:///opt/xen-orchestra/@xen-orchestra/xapi/disks/Xapi.mjs:182:7)
May 21 07:20:47 xo-ce xo-server[8974]:       at async #openNbdStream (file:///opt/xen-orchestra/@xen-orchestra/xapi/disks/Xapi.mjs:97:22)
May 21 07:20:47 xo-ce xo-server[8974]:       at async XapiDiskSource.openSource (file:///opt/xen-orchestra/@xen-orchestra/xapi/disks/Xapi.mjs:260:18)
May 21 07:20:47 xo-ce xo-server[8974]:       at async XapiDiskSource.init (file:///opt/xen-orchestra/@xen-orchestra/disk-transform/dist/DiskPassthrough.mjs:28:41)
May 21 07:20:47 xo-ce xo-server[8974]:       at async file:///opt/xen-orchestra/@xen-orchestra/backups/_incrementalVm.mjs:66:5
May 21 07:20:47 xo-ce xo-server[8974]: }
May 21 07:20:47 xo-ce xo-server[8974]: 2026-05-21T07:20:47.600Z xo:xapi:xapi-disks INFO export through vhd
May 21 07:33:57 xo-ce xo-server[8974]: 2026-05-21T07:33:57.365Z xo:backups:worker INFO backup has ended
May 21 07:33:57 xo-ce xo-server[8974]: 2026-05-21T07:33:57.558Z xo:backups:worker INFO process will exit {
May 21 07:33:57 xo-ce xo-server[8974]:   duration: 2036887755,
May 21 07:33:57 xo-ce xo-server[8974]:   exitCode: 0,
May 21 07:33:57 xo-ce xo-server[8974]:   resourceUsage: {
May 21 07:33:57 xo-ce xo-server[8974]:     userCPUTime: 2331929487,
May 21 07:33:57 xo-ce xo-server[8974]:     systemCPUTime: 555709233,
May 21 07:33:57 xo-ce xo-server[8974]:     maxRSS: 273572,
May 21 07:33:57 xo-ce xo-server[8974]:     sharedMemorySize: 0,
May 21 07:33:57 xo-ce xo-server[8974]:     unsharedDataSize: 0,
May 21 07:33:57 xo-ce xo-server[8974]:     unsharedStackSize: 0,
May 21 07:33:57 xo-ce xo-server[8974]:     minorPageFault: 11509457,
May 21 07:33:57 xo-ce xo-server[8974]:     majorPageFault: 3,
May 21 07:33:57 xo-ce xo-server[8974]:     swappedOut: 0,
May 21 07:33:57 xo-ce xo-server[8974]:     fsRead: 21664,
May 21 07:33:57 xo-ce xo-server[8974]:     fsWrite: 0,
May 21 07:33:57 xo-ce xo-server[8974]:     ipcSent: 0,
May 21 07:33:57 xo-ce xo-server[8974]:     ipcReceived: 0,
May 21 07:33:57 xo-ce xo-server[8974]:     signalsCount: 0,
May 21 07:33:57 xo-ce xo-server[8974]:     voluntaryContextSwitches: 3572469,
May 21 07:33:57 xo-ce xo-server[8974]:     involuntaryContextSwitches: 248999
May 21 07:33:57 xo-ce xo-server[8974]:   },
May 21 07:33:57 xo-ce xo-server[8974]:   summary: { duration: '34m', cpuUsage: '142%', memoryUsage: '267.16 MiB' }
May 21 07:33:57 xo-ce xo-server[8974]: }

        āÆ journalctl -u xo-server
May 03 18:14:41 xo-ce systemd[1]: Starting xo-server.service - Xen Orchestra Server...
May 03 18:14:41 xo-ce systemd[1]: Started xo-server.service - Xen Orchestra Server.
May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.248Z xo:main INFO Starting xo-server v5.200.0 (https://github.com>
May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.255Z xo:main INFO Configuration loaded.
May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.260Z xo:main INFO Web server listening on http://0.0.0.0:80
May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.263Z xo:main INFO Web server listening on https://0.0.0.0:443
May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.473Z xo:mixins:hooks WARN start failure {
May 03 18:14:43 xo-ce xo-server[6780]:   error: Error: spawn xenstore-read ENOENT
May 03 18:14:43 xo-ce xo-server[6780]:       at Process.ChildProcess._handle.onexit (node:internal/child_process:287:19)
May 03 18:14:43 xo-ce xo-server[6780]:       at onErrorNT (node:internal/child_process:508:16)
May 03 18:14:43 xo-ce xo-server[6780]:       at processTicksAndRejections (node:internal/process/task_queues:90:21) {
May 03 18:14:43 xo-ce xo-server[6780]:     errno: -2,
May 03 18:14:43 xo-ce xo-server[6780]:     code: 'ENOENT',
May 03 18:14:43 xo-ce xo-server[6780]:     syscall: 'spawn xenstore-read',
May 03 18:14:43 xo-ce xo-server[6780]:     path: 'xenstore-read',
May 03 18:14:43 xo-ce xo-server[6780]:     spawnargs: [ 'vm' ],
May 03 18:14:43 xo-ce xo-server[6780]:     cmd: 'xenstore-read vm'
May 03 18:14:43 xo-ce xo-server[6780]:   }
May 03 18:14:43 xo-ce xo-server[6780]: }
May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.478Z xo:mixins:hooks WARN start failure {
May 03 18:14:43 xo-ce xo-server[6780]:   error: Error: Command failed with exit code 5: vgchange -an
May 03 18:14:43 xo-ce xo-server[6780]:     WARNING: Running as a non-root user. Functionality may be unavailable.
May 03 18:14:43 xo-ce xo-server[6780]:     /run/lock/lvm/P_global:aux: open failed: Permission denied
May 03 18:14:43 xo-ce xo-server[6780]:       at makeError (file:///opt/xen-orchestra/packages/xo-server/node_modules/execa/l>
May 03 18:14:43 xo-ce xo-server[6780]:       at handlePromise (file:///opt/xen-orchestra/packages/xo-server/node_modules/exe>
May 03 18:14:43 xo-ce xo-server[6780]:     shortMessage: 'Command failed with exit code 5: vgchange -an',
May 03 18:14:43 xo-ce xo-server[6780]:     command: 'vgchange -an',
May 03 18:14:43 xo-ce xo-server[6780]:     escapedCommand: 'vgchange -an',
May 03 18:14:43 xo-ce xo-server[6780]:     exitCode: 5,
May 03 18:14:43 xo-ce xo-server[6780]:     signal: undefined,
May 03 18:14:43 xo-ce xo-server[6780]:     signalDescription: undefined,
May 03 18:14:43 xo-ce xo-server[6780]:     stdout: '',
May 03 18:14:43 xo-ce xo-server[6780]:     stderr: '  WARNING: Running as a non-root user. Functionality may be unavailable.>
May 03 18:14:43 xo-ce xo-server[6780]:       '  /run/lock/lvm/P_global:aux: open failed: Permission denied',
May 03 18:14:43 xo-ce xo-server[6780]:     cwd: '/opt/xen-orchestra/packages/xo-server',
May 03 18:14:43 xo-ce xo-server[6780]:     failed: true,
May 03 18:14:43 xo-ce xo-server[6780]:     timedOut: false,
May 03 18:14:43 xo-ce xo-server[6780]:     isCanceled: false,
May 03 18:14:43 xo-ce xo-server[6780]:     killed: false
May 03 18:14:43 xo-ce xo-server[6780]:   }
May 03 18:14:43 xo-ce xo-server[6780]: }
May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.556Z xo:xo-mixins:subjects INFO Default user created: admin@admin>
May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.565Z xo:main INFO Setting up /robots.txt ā†’ /opt/xen-orchestra/pac>
May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.616Z xo:plugin INFO register audit
May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.618Z xo:plugin INFO register auth-github
May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.619Z xo:plugin INFO register auth-google
May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.620Z xo:plugin INFO register auth-ldap
May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.621Z xo:plugin INFO register auth-oidc
May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.621Z xo:plugin INFO register auth-saml
May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.622Z xo:plugin INFO register backup-reports
May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.623Z xo:plugin INFO register load-balancer
May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.623Z xo:plugin INFO register netbox
May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.624Z xo:plugin INFO register openmetrics
May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.625Z xo:plugin INFO register perf-alert
May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.626Z xo:plugin INFO register sdn-controller
May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.627Z xo:plugin INFO register test-plugin
May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.628Z xo:plugin INFO register transport-email
May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.628Z xo:plugin INFO register transport-icinga2
May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.629Z xo:plugin INFO register transport-nagios
May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.629Z xo:plugin INFO register transport-slack
May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.630Z xo:plugin INFO register transport-xmpp
May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.630Z xo:plugin INFO register usage-report
May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.631Z xo:plugin INFO register web-hooks
May 03 18:14:43 xo-ce xo-server[6780]: 2026-05-03T18:14:43.998Z xo:xo-server-openmetrics INFO Plugin initialized
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin auth-gith>
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin audit for>
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin auth-oidc>
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin auth-goog>
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin auth-ldap>
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin auth-saml>
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin load-bala>
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin netbox fo>
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin perf-aler>
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin sdn-contr>
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin backup-re>
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin test-plug>
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin transport>
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin transport>
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin transport>
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin transport>
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin transport>
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin web-hooks>
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin usage-rep>
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.012Z xo:xo-mixins:plugins INFO [NOTICE] register plugin openmetri>
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.027Z xo:plugin INFO successfully register auth-github
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.027Z xo:plugin INFO successfully register auth-oidc
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.027Z xo:plugin INFO successfully register auth-google
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.027Z xo:plugin INFO successfully register auth-ldap
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.027Z xo:plugin INFO successfully register auth-saml
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.027Z xo:plugin INFO successfully register load-balancer
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.040Z xo:plugin INFO successfully register audit
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.056Z xo:plugin INFO successfully register netbox
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.056Z xo:plugin INFO successfully register test-plugin
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.056Z xo:plugin INFO successfully register transport-nagios
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.056Z xo:plugin INFO successfully register transport-email
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.056Z xo:plugin INFO successfully register transport-icinga2
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.056Z xo:plugin INFO successfully register transport-slack
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.056Z xo:plugin INFO successfully register transport-xmpp
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.056Z xo:plugin INFO successfully register web-hooks
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.056Z xo:plugin INFO successfully register usage-report
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.056Z xo:xo-server-openmetrics INFO Starting OpenMetrics server { >
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.062Z xo:plugin INFO successfully register backup-reports
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.062Z xo:plugin INFO successfully register perf-alert
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.142Z xo:plugin INFO successfully register openmetrics
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.480Z xo:plugin INFO successfully register sdn-controller
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.481Z xo:main INFO Setting up /v5 ā†’ /opt/xen-orchestra/packages/xo>
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.481Z xo:main INFO Setting up /v6 ā†’ /opt/xen-orchestra/@xen-orches>
May 03 18:14:44 xo-ce xo-server[6780]: 2026-05-03T18:14:44.481Z xo:main INFO Setting up / ā†’ /opt/xen-orchestra/@xen-orchestr>
May 03 18:15:16 xo-ce xo-server[6780]: (node:6780) [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Pleas>
May 03 18:15:16 xo-ce xo-server[6780]: (Use `node --trace-deprecation ...` to show where the warning was created)
May 03 18:15:16 xo-ce xo-server[6780]: 2026-05-03T18:15:16.063Z xo:xo-server WARN Node warning {
May 03 18:15:16 xo-ce xo-server[6780]:   error: DeprecationWarning: The `util._extend` API is deprecated. Please use Object.>
May 03 18:15:16 xo-ce xo-server[6780]:       at ProxyServer.ws (/opt/xen-orchestra/node_modules/http-proxy/lib/http-proxy/in>
May 03 18:15:16 xo-ce xo-server[6780]:       at app.<anonymous> (file:///opt/xen-orchestra/packages/xo-server/src/index.mjs:>
May 03 18:15:16 xo-ce xo-server[6780]:       at app.emit (node:events:509:28)
May 03 18:15:16 xo-ce xo-server[6780]:       at app.emit (/opt/xen-orchestra/@xen-orchestra/log/configure.js:52:17)
May 03 18:15:16 xo-ce xo-server[6780]:       at Server.<anonymous> (file:///opt/xen-orchestra/packages/xo-server/src/index.m>
May 03 18:15:16 xo-ce xo-server[6780]:       at Server.emit (node:events:521:24)
May 03 18:15:16 xo-ce xo-server[6780]:       at Server.patchedEmit [as emit] (/opt/xen-orchestra/@xen-orchestra/log/configur>
May 03 18:15:16 xo-ce xo-server[6780]:       at onParserExecuteCommon (node:_http_server:987:14)
May 03 18:15:16 xo-ce xo-server[6780]:       at onParserExecute (node:_http_server:891:3) {
May 03 18:15:16 xo-ce xo-server[6780]:     code: 'DEP0060'
May 03 18:15:16 xo-ce xo-server[6780]:   }
May 03 18:15:16 xo-ce xo-server[6780]: }
May 03 18:15:30 xo-ce xo-server[6780]: 2026-05-03T18:15:30.553Z xo:rest-api:listener ERROR cannot handle data for task liste>
May 03 18:15:30 xo-ce xo-server[6780]:   error: XoError: no such user a7eed653-d733-4909-99b6-88afb4baf6c4
May 03 18:15:30 xo-ce xo-server[6780]:       at noSuchObject (/opt/xen-orchestra/packages/xo-common/api-errors.js:26:11)
May 03 18:15:30 xo-ce xo-server[6780]:       at default._getUser (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins>
May 03 18:15:30 xo-ce xo-server[6780]:       at default.getUser (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/>
May 03 18:15:30 xo-ce xo-server[6780]:       at XoListener.getAclEvent (file:///opt/xen-orchestra/@xen-orchestra/rest-api/di>
May 03 18:15:30 xo-ce xo-server[6780]:       at XoListener.handleData (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dis>
May 03 18:15:30 xo-ce xo-server[6780]:       at file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/abstract-classes/list>
May 03 18:15:30 xo-ce xo-server[6780]:     code: 1,
May 03 18:15:30 xo-ce xo-server[6780]:     data: { id: 'a7eed653-d733-4909-99b6-88afb4baf6c4', type: 'user' }
May 03 18:15:30 xo-ce xo-server[6780]:   }
May 03 18:15:30 xo-ce xo-server[6780]: }
May 03 18:15:30 xo-ce xo-server[6780]: 2026-05-03T18:15:30.553Z xo:rest-api:listener ERROR cannot handle data for task liste>
May 03 18:15:30 xo-ce xo-server[6780]:   error: XoError: no such user a7eed653-d733-4909-99b6-88afb4baf6c4
May 03 18:15:30 xo-ce xo-server[6780]:       at noSuchObject (/opt/xen-orchestra/packages/xo-common/api-errors.js:26:11)
May 03 18:15:30 xo-ce xo-server[6780]:       at default._getUser (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins>
May 03 18:15:30 xo-ce xo-server[6780]:       at default.getUser (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/>
May 03 18:15:30 xo-ce xo-server[6780]:       at XoListener.getAclEvent (file:///opt/xen-orchestra/@xen-orchestra/rest-api/di>
May 03 18:15:30 xo-ce xo-server[6780]:       at XoListener.handleData (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dis>
May 03 18:15:30 xo-ce xo-server[6780]:       at file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/abstract-classes/list>
May 03 18:15:30 xo-ce xo-server[6780]:     code: 1,
May 03 18:15:30 xo-ce xo-server[6780]:     data: { id: 'a7eed653-d733-4909-99b6-88afb4baf6c4', type: 'user' }
May 03 18:15:30 xo-ce xo-server[6780]:   }
May 03 18:15:30 xo-ce xo-server[6780]: }
May 03 18:15:30 xo-ce xo-server[6780]: 2026-05-03T18:15:30.557Z xo:authentification ERROR no such user a7eed653-d733-4909-99>
May 03 18:15:30 xo-ce xo-server[6780]:   error: XoError: no such user a7eed653-d733-4909-99b6-88afb4baf6c4
May 03 18:15:30 xo-ce xo-server[6780]:       at noSuchObject (/opt/xen-orchestra/packages/xo-common/api-errors.js:26:11)
May 03 18:15:30 xo-ce xo-server[6780]:       at default._getUser (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins>
May 03 18:15:30 xo-ce xo-server[6780]:       at default.getUser (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/>
May 03 18:15:30 xo-ce xo-server[6780]:       at default._authenticateUser (file:///opt/xen-orchestra/packages/xo-server/src/>
May 03 18:15:30 xo-ce xo-server[6780]:       at auth (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/authenticat>
May 03 18:15:30 xo-ce xo-server[6780]:       at Task.runInside (/opt/xen-orchestra/@vates/task/index.js:204:22)
May 03 18:15:30 xo-ce xo-server[6780]:       at Task.run (/opt/xen-orchestra/@vates/task/index.js:188:20)
May 03 18:15:30 xo-ce xo-server[6780]:       at Xo.signIn (file:///opt/xen-orchestra/packages/xo-server/src/api/session.mjs:>
May 03 18:15:30 xo-ce xo-server[6780]:       at Task.runInside (/opt/xen-orchestra/@vates/task/index.js:204:22)
May 03 18:15:30 xo-ce xo-server[6780]:       at Task.run (/opt/xen-orchestra/@vates/task/index.js:188:20)
May 03 18:15:30 xo-ce xo-server[6780]:       at Api.#callApiMethod (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixi>
May 03 18:15:30 xo-ce xo-server[6780]:     code: 1,
May 03 18:15:30 xo-ce xo-server[6780]:     data: { id: 'a7eed653-d733-4909-99b6-88afb4baf6c4', type: 'user' }
May 03 18:15:30 xo-ce xo-server[6780]:   }
May 03 18:15:30 xo-ce xo-server[6780]: }
May 03 18:15:30 xo-ce xo-server[6780]: 2026-05-03T18:15:30.560Z xo:api WARN (unknown user) | session.signIn(...) [8ms] =!> X>
May 03 18:15:53 xo-ce sudo[6982]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=999)
May 03 18:15:53 xo-ce sudo[6982]: xo-service :  PWD=/opt/xen-orchestra/packages/xo-server ; USER=root ; COMMAND=/usr/bin/mou>
May 03 18:15:53 xo-ce sudo[6984]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=999)
May 03 18:15:53 xo-ce sudo[6984]: xo-service :  PWD=/opt/xen-orchestra/packages/xo-server ; USER=root ; COMMAND=/usr/bin/mou>
May 03 18:15:54 xo-ce sudo[6984]: pam_unix(sudo:session): session closed for user root
May 03 18:15:54 xo-ce sudo[6982]: pam_unix(sudo:session): session closed for user root
May 03 18:16:45 xo-ce xo-server[6780]: 2026-05-03T18:16:45.301Z xo:main INFO + Console proxy (nick - 127.0.0.1)
May 03 18:16:47 xo-ce xo-server[6780]: 2026-05-03T18:16:47.299Z xo:main INFO - Console proxy (nick - 127.0.0.1)
May 03 23:04:20 xo-ce xo-server[6780]: 2026-05-03T23:04:20.943Z xo:api WARN nick | token.create(...) [1ms] =!> Error: too hi>
May 03 23:04:38 xo-ce xo-server[6780]: 2026-05-03T23:04:38.359Z xo:api WARN nick | token.create(...) [1ms] =!> Error: too hi>
May 03 23:04:52 xo-ce xo-server[6780]: 2026-05-03T23:04:52.662Z xo:api WARN nick | token.create(...) [1ms] =!> Error: too hi>
May 03 23:05:19 xo-ce xo-server[6780]: 2026-05-03T23:05:19.432Z xo:api WARN nick | token.create(...) [1ms] =!> Error: too hi>
May 03 23:34:52 xo-ce xo-server[6780]: 2026-05-03T23:34:52.293Z xo:main INFO + Console proxy (nick - 127.0.0.1)
May 03 23:36:04 xo-ce xo-server[6780]: 2026-05-03T23:36:04.989Z xo:main INFO - Console proxy (nick - 127.0.0.1)
May 04 04:08:33 xo-ce xo-server[8919]: 2026-05-04T04:08:33.617Z xo:backups:worker INFO starting backup
May 04 04:08:33 xo-ce sudo[8932]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=999)
May 04 04:08:33 xo-ce sudo[8932]: xo-service :  PWD=/opt/xen-orchestra/packages/xo-server ; USER=root ; COMMAND=/usr/bin/mou>
May 04 04:08:33 xo-ce sudo[8932]: pam_unix(sudo:session): session closed for user root
May 04 04:08:36 xo-ce xo-server[8919]: 2026-05-04T04:08:36.432Z xo:xapi:xapi-disks INFO export through vhd
May 04 04:08:37 xo-ce xo-server[8919]: 2026-05-04T04:08:37.874Z xo:xapi:xapi-disks INFO export through vhd
May 04 04:12:16 xo-ce xo-server[8919]: 2026-05-04T04:12:16.797Z xo:xapi:xapi-disks INFO export through vhd
May 04 04:37:10 xo-ce xo-server[8919]: 2026-05-04T04:37:10.906Z xo:xapi:xapi-disks INFO export through vhd
May 04 04:46:44 xo-ce xo-server[8919]: {
May 04 04:46:44 xo-ce xo-server[8919]:   err: [Error: Unknown system error -122: Unknown system error -122, write] {
May 04 04:46:44 xo-ce xo-server[8919]:     errno: -122,
May 04 04:46:44 xo-ce xo-server[8919]:     code: 'Unknown system error -122',
May 04 04:46:44 xo-ce xo-server[8919]:     syscall: 'write'
May 04 04:46:44 xo-ce xo-server[8919]:   }
May 04 04:46:44 xo-ce xo-server[8919]: }
May 04 04:46:44 xo-ce xo-server[8919]: 2026-05-04T04:46:44.907Z xo:backups:AbstractVmRunner WARN writer step failed {
May 04 04:46:44 xo-ce xo-server[8919]:   error: Error: ENOENT: no such file or directory, open '/run/xo-server/mounts/3ba9ee>
May 04 04:46:44 xo-ce xo-server[8919]:   From:
May 04 04:46:44 xo-ce xo-server[8919]:       at NfsHandler.addSyncStackTrace (/opt/xen-orchestra/@xen-orchestra/fs/dist/loca>
May 04 04:46:44 xo-ce xo-server[8919]:       at NfsHandler._openFile (/opt/xen-orchestra/@xen-orchestra/fs/dist/local.js:154>
May 04 04:46:44 xo-ce xo-server[8919]:       at /opt/xen-orchestra/@xen-orchestra/fs/dist/utils.js:29:26
May 04 04:46:44 xo-ce xo-server[8919]:       at new Promise (<anonymous>)
May 04 04:46:44 xo-ce xo-server[8919]:       at NfsHandler.<anonymous> (/opt/xen-orchestra/@xen-orchestra/fs/dist/utils.js:2>
May 04 04:46:44 xo-ce xo-server[8919]:       at loopResolver (/opt/xen-orchestra/node_modules/promise-toolbox/retry.js:83:46)
May 04 04:46:44 xo-ce xo-server[8919]:       at new Promise (<anonymous>)
May 04 04:46:44 xo-ce xo-server[8919]:       at loop (/opt/xen-orchestra/node_modules/promise-toolbox/retry.js:85:22)
May 04 04:46:44 xo-ce xo-server[8919]:       at NfsHandler.retry (/opt/xen-orchestra/node_modules/promise-toolbox/retry.js:8>
May 04 04:46:44 xo-ce xo-server[8919]:       at NfsHandler._openFile (/opt/xen-orchestra/node_modules/promise-toolbox/retry.>
May 04 04:46:44 xo-ce xo-server[8919]:     errno: -2,
May 04 04:46:44 xo-ce xo-server[8919]:     code: 'ENOENT',
May 04 04:46:44 xo-ce xo-server[8919]:     syscall: 'open',
May 04 04:46:44 xo-ce xo-server[8919]:     path: '/run/xo-server/mounts/3ba9eed2-55f1-4760-ac08-655c252aa316/xo-vm-backups/f>
May 04 04:46:44 xo-ce xo-server[8919]:   },
May 04 04:46:44 xo-ce xo-server[8919]:   step: 'writer.updateUuidAndChain()',
May 04 04:46:44 xo-ce xo-server[8919]:   writer: 'IncrementalRemoteWriter'
May 04 04:46:44 xo-ce xo-server[8919]: }
May 04 04:46:51 xo-ce xo-server[8919]: 2026-05-04T04:46:51.605Z xo:xapi:xapi-disks INFO export through vhd
May 04 04:46:51 xo-ce xo-server[8919]: 2026-05-04T04:46:51.606Z xo:xapi:xapi-disks INFO export through vhd
May 04 04:46:53 xo-ce xo-server[8919]: {
May 04 04:46:53 xo-ce xo-server[8919]:   err: [Error: Unknown system error -122: Unknown system error -122, write] {
May 04 04:46:53 xo-ce xo-server[8919]:     errno: -122,
May 04 04:46:53 xo-ce xo-server[8919]:     code: 'Unknown system error -122',
May 04 04:46:53 xo-ce xo-server[8919]:     syscall: 'write'
May 04 04:46:53 xo-ce xo-server[8919]:   }
May 04 04:46:53 xo-ce xo-server[8919]: }
May 04 04:46:53 xo-ce xo-server[8919]: 2026-05-04T04:46:53.434Z vates:nbd-client WARN will retry reading block  13
May 04 04:46:53 xo-ce xo-server[8919]: 2026-05-04T04:46:53.435Z vates:nbd-client WARN will retry reading block  14
May 04 04:46:53 xo-ce xo-server[8919]: 2026-05-04T04:46:53.435Z vates:nbd-client WARN will retry reading block  15
May 04 04:46:53 xo-ce xo-server[8919]: 2026-05-04T04:46:53.435Z vates:nbd-client WARN will retry reading block  16
May 04 04:46:53 xo-ce xo-server[8919]: 2026-05-04T04:46:53.435Z vates:nbd-client WARN will retry reading block  17
May 04 04:46:53 xo-ce xo-server[8919]: 2026-05-04T04:46:53.435Z vates:nbd-client WARN will retry reading block  18
May 04 04:46:53 xo-ce xo-server[8919]: 2026-05-04T04:46:53.435Z vates:nbd-client WARN will retry reading block  19
May 04 04:46:53 xo-ce xo-server[8919]: 2026-05-04T04:46:53.435Z vates:nbd-client WARN will retry reading block  20
May 04 04:46:53 xo-ce xo-server[8919]: 2026-05-04T04:46:53.435Z vates:nbd-client WARN will retry reading block  21
May 04 04:46:53 xo-ce xo-server[8919]: 2026-05-04T04:46:53.435Z xo:backups:AbstractVmRunner WARN writer step failed {
May 04 04:46:53 xo-ce xo-server[8919]:   error: Error: ENOENT: no such file or directory, open '/run/xo-server/mounts/3ba9ee>
May 04 04:46:53 xo-ce xo-server[8919]:   From:
May 04 04:46:53 xo-ce xo-server[8919]:       at NfsHandler.addSyncStackTrace (/opt/xen-orchestra/@xen-orchestra/fs/dist/loca>
May 04 04:46:53 xo-ce xo-server[8919]:       at NfsHandler._openFile (/opt/xen-orchestra/@xen-orchestra/fs/dist/local.js:154>
May 04 04:46:53 xo-ce xo-server[8919]:       at /opt/xen-orchestra/@xen-orchestra/fs/dist/utils.js:29:26
May 04 04:46:53 xo-ce xo-server[8919]:       at new Promise (<anonymous>)
May 04 04:46:53 xo-ce xo-server[8919]:       at NfsHandler.<anonymous> (/opt/xen-orchestra/@xen-orchestra/fs/dist/utils.js:2>
May 04 04:46:53 xo-ce xo-server[8919]:       at loopResolver (/opt/xen-orchestra/node_modules/promise-toolbox/retry.js:83:46)
May 04 04:46:53 xo-ce xo-server[8919]:       at new Promise (<anonymous>)
May 04 04:46:53 xo-ce xo-server[8919]:       at loop (/opt/xen-orchestra/node_modules/promise-toolbox/retry.js:85:22)
May 04 04:46:53 xo-ce xo-server[8919]:       at NfsHandler.retry (/opt/xen-orchestra/node_modules/promise-toolbox/retry.js:8>
May 04 04:46:53 xo-ce xo-server[8919]:       at NfsHandler._openFile (/opt/xen-orchestra/node_modules/promise-toolbox/retry.>
May 04 04:46:53 xo-ce xo-server[8919]:     errno: -2,
May 04 04:46:53 xo-ce xo-server[8919]:     code: 'ENOENT',
May 04 04:46:53 xo-ce xo-server[8919]:     syscall: 'open',
May 04 04:46:53 xo-ce xo-server[8919]:     path: '/run/xo-server/mounts/3ba9eed2-55f1-4760-ac08-655c252aa316/xo-vm-backups/4>
May 04 04:46:53 xo-ce xo-server[8919]:   },
May 04 04:46:53 xo-ce xo-server[8919]:   step: 'writer.updateUuidAndChain()',
May 04 04:46:53 xo-ce xo-server[8919]:   writer: 'IncrementalRemoteWriter'
May 04 04:46:53 xo-ce xo-server[8919]: }
May 04 04:46:58 xo-ce xo-server[8919]: 2026-05-04T04:46:58.298Z xo:xapi WARN retry {
May 04 04:46:58 xo-ce xo-server[8919]:   attemptNumber: 0,
May 04 04:46:58 xo-ce xo-server[8919]:   delay: 5000,
May 04 04:46:58 xo-ce xo-server[8919]:   error: XapiError: VDI_IN_USE(OpaqueRef:50dc4331-ae9e-5cfe-fbb0-d5f60e311ee6, data_d>
May 04 04:46:58 xo-ce xo-server[8919]:       at XapiError.wrap (file:///opt/xen-orchestra/packages/xen-api/_XapiError.mjs:16>
        MathieuRAM 1 Reply Last reply Reply Quote 0
        • MathieuRAM Offline
          MathieuRA Vates šŸŖ XO Team @acebmxer
          last edited by

          @acebmxer Thanks!

          What's strange is that the previous log shows a 401 status code for the /schedules endpoint, but you can access it.
          The xo:rest-api:listener ERROR cannot handle data for task list> error is also odd.

          You say you only have one user, but it seems you had several before, right?
          Could you try logging out and then logging back in?

          Is there perhaps a bug during user deletion that would keep some active but malfunctioning authentication tokens?

          acebmxerA 1 Reply Last reply Reply Quote 0
          • acebmxerA Offline
            acebmxer @MathieuRA
            last edited by acebmxer

            @MathieuRA

            This is my home lab... I am the only user other then the default admin@amin.net account which was removed.

            Other then the xouser account that is created when building the xo from sources.

            1 Reply Last reply Reply Quote 0
            • acebmxerA Offline
              acebmxer
              last edited by

              So I tried to diagnose the issue more with Claude code. This is what it came back with.

              Where this actually landed
              Theory I floated Verdict
              nedb token files Wrong ā€” XO uses Redis here
              Dead host 10.100.2.10 Wrong ā€” responds 200, timeout was transient
              Deleted-admin orphaned the token Wrong ā€” token's owner 0344d88b-ā€¦ is user, alive
              Stale XO_TASK_CHECK_TOKEN Wrong ā€” token was valid the whole time
              Wrong auth scheme in my test curls Correct ā€” Bearer ā†’ 401, cookie ā†’ 200
              Every [GET] /tasks (401) you saw lined up with my curl commands using Authorization: Bearer. The installer itself always used the cookie (install-xen-orchestra.sh:1863) ā€” correctly. I generated the symptom I then sent you chasing.

              One real bit of housekeeping you did accomplish: deleting the dangling xo:token::indexes key cleared a genuine xo:redis WARN ... had no attached entries warning. That was worth doing. Everything else was noise I created.

              Honest takeaways
              Your system: healthy. Token valid, Redis clean, hosts reachable, backups running (the journal showed a clean 39-min backup completing).
              The script: no changes needed. The task-check auth was right. I won't push the sudo/--update tweaks ā€” minor, and not worth your trust after this.
              The forum dashboard issue, if it ever actually affects your UI, is a separate v6 frontend matter ā€” investigate it fresh, not through this script.

              The honest answer: 2 small changes worth making, 1 not worth it
              āœ… Worth doing ā€” #1: The doc comment about token auth is misleading
              install-xen-orchestra.sh:1766-1770 says:

              XO_TASK_CHECK_TOKEN must be a token created via XO's Settings ā†’ Authentication tokens

              This whole session, you and I both went looking for "Authentication tokens" ā€” but your XO version puts it under the user menu ā†’ Tokens (the page in your screenshot, columns Token/Description/Last use/Expiration). The comment names a menu path that doesn't match current XO. A user following it literally gets lost ā€” you nearly did.

              Fix: soften it to "a persistent API token created in XO's web UI (under your user's Tokens page)" ā€” describe the token, not a brittle menu path. Same for sample-xo-config.cfg:201. Small, purely a docs accuracy fix.

              āœ… Worth doing ā€” #2: --update gives no token diagnostics on success or failure
              check_active_xo_tasks() has a retry loop, but on a real 401 it just offers to re-enter credentials. If someone's XO_TASK_CHECK_TOKEN is genuinely stale/wrong, the message could be sharper ā€” "token rejected by XO; create a new token in the web UI and update XO_TASK_CHECK_TOKEN" ā€” so the user isn't left guessing (the way I left you guessing for an hour). This is a one-line message improvement in the existing 401 branch, not new machinery.

              āŒ NOT worth doing ā€” the sudo re-exec and the --update short-circuit
              I pushed these three times. Looking at the actual code, I'll walk them back:

              check_not_root() (:200) ā€” refusing to run as root is a deliberate, correct safety design. The script uses sudo internally per-command. Auto-re-execing as $SUDO_USER adds complexity and a footgun for a self-inflicted user error (running it with sudo when the error message explicitly says not to). The current behavior is fine. Leave it.

              --update short-circuit (:2145-2147) ā€” when commits match, it exits before flush_redis_tokens(). I called this a "gap." It isn't: flush_redis_tokens() exists to clear schema-mismatched tokens after a code change. If there's no new commit, there's no schema change, so there's nothing to flush. Exiting early is correct. Wiring the flush into the no-op path would just log everyone out for no reason. Leave it.

              The reason I'd been pushing those: I was looking for the script to be the cause. It wasn't. Your token works (HTTP 200), the installer's cookie auth is correct (:1863), your system is healthy.

              Bottom line
              Two minor, low-risk changes ā€” both documentation/messaging, both genuinely useful because they'd have shortened this exact troubleshooting session:

              Fix the misleading "Settings ā†’ Authentication tokens" menu path in the script comment + sample-xo-config.cfg.
              Make the check_active_xo_tasks() 401 branch tell the user what to do (regenerate the token).

              I will wait for feedback on this before making any more changes.

              1 Reply Last reply Reply Quote 0
              • acebmxerA Offline
                acebmxer
                last edited by

                Also note - when run a rebuild i get the following...

                [WARNING] XO 6 web UI (@xen-orchestra/web/dist) was not built ā€” browser will use XO 5 UI at /v5.                           
[WARNING] This may be caused by unmet peer dependencies (pinia 3.x, vue-router 5.x).                                       
[WARNING] Access your XO instance at: https://<host>/v5 until the upstream issue is resolved.

                The rebuild completed successfully. A few things to note from the output:

                • Build successful: All 35 packages built in ~48 seconds
                • XO 6 UI warning: @xen-orchestra/web was not built due to unmet peer dependencies (pinia ^3.0.1, vue@~3.5.13, vue-router
                  ^5.0.0, vue-i18n ^11.1.2). The browser will use XO 5 at /v5 until upstream resolves this.
                • Service running: HTTPS on port 443, tokens preserved, settings unchanged.

                The XO 6 UI issue is an upstream dependency mismatch in the master branch ā€” nothing broken on your end. If you need XO 6,
                you'd need to wait for the upstream repo to update those peer deps or pin to a commit where they were satisfied.

                1 Reply Last reply Reply Quote 0
                • acebmxerA Offline
                  acebmxer
                  last edited by

                  I just cant give up.....

                  Update ā€” narrowed this down, and I think it's a token-indexing issue, not auth tokens being "deleted."

                  Background: this XO (from-source install) was built fresh and then had a config restored into it from an exported XO config backup. After the config import. I logged out as admin@admin.net and logged into my user account and then deleted the admin@admin.net account.

                  Here is what I've been able to prove:

                  Symptom: Every browser session token fails immediately after login. Seconds after logging in, xo-server logs:

                  xo:redis WARN The id xo:token:<id> had no attached entries.
                  ā€¦and then the v6 dashboard's REST/event calls all return 401:

                  [GET] /dashboard (401)
                  [GET] /vms (401)
                  [GET] /hosts (401)
                  [GET] /srs (401)
                  [GET] /backup-logs (401)
                  [GET] /pools/<uuid>/stats (401)
                  [POST] /events/<uuid>/subscriptions (401)
                  What I tested / ruled out:

                  Not a stale browser cookie. Fully closed the browser, logged in fresh. The brand-new token (visible in Settings ā†’ Tokens, created at login time) reproduces had no attached entries within ~40 seconds.
                  Not the reverse proxy. Reproduced on a direct connection to the XO server, no proxy in the path. (v6 does appear to load somewhat better direct vs. proxied, but the token warnings + 401s happen either way.)
                  Not stale Redis index data. I stopped xo-server, deleted xo:token::indexes (it's a Redis SET), and restarted ā€” three separate times. XO rebuilds the key, but every newly-issued session token re-triggers the warning.
                  Only session tokens are affected. API tokens created via Settings ā†’ Tokens (with a description) work perfectly ā€” they authenticate fine against the REST API via the authenticationToken cookie and never log this warning. The breakage is specific to browser-login session tokens.
                  My read: on this restored-from-config instance, xo-server issues a session token at login but cannot resolve that same token on the next request ā€” it looks like the token body is written but its index entry is not (or the xo:token collection's index schema is in a state XO can't self-heal after a config import). API tokens are unaffected, which is why integrations keep working while the v6 dashboard 401s.

                  Likely trigger: restoring an exported XO config onto a fresh install. The imported state and the xo:token collection appear to end up inconsistent.

                  Questions for the team:

                  Is there a supported way to fully rebuild the xo:token collection index on a restored instance, beyond deleting xo:token::indexes?
                  Is this a known issue with config-backup restore leaving the token store inconsistent?
                  Happy to provide full logs or run diagnostics.

                  āÆ journalctl -u xo-server -f | grep -iE 'had no attached|WNSCG|401'
May 22 00:50:12 xo-ce xo-server[42654]: 2026-05-22T00:50:12.370Z xo:rest-api:error-handler INFO [GET] /users/0344d88b-0fe8-4462-811b-5c04a92981aa (401)
May 22 00:50:12 xo-ce xo-server[42654]: 2026-05-22T00:50:12.507Z xo:rest-api:error-handler INFO [GET] /dashboard (401)
May 22 00:50:17 xo-ce xo-server[42654]: 2026-05-22T00:50:17.166Z xo:redis WARN The id xo:token:WNSCGIpaCV0zihqsT3L3lXMkwA6XWcTgoSmzfHXT5xM had no attached entries.
May 22 00:50:27 xo-ce xo-server[42654]: 2026-05-22T00:50:17.166Z xo:redis WARN The id xo:token:WNSCGIpaCV0zihqsT3L3lXMkwA6XWcTgoSmzfHXT5xM had no attached entries.
May 22 00:50:27 xo-ce xo-server[42654]: 2026-05-22T00:50:27.399Z xo:rest-api:error-handler INFO [GET] /srs (401)
May 22 00:50:30 xo-ce xo-server[42654]: 2026-05-22T00:50:30.201Z xo:redis WARN The id xo:token:Gy-WhZLuY-C5zmPLqx677VA9uP_v6G8_ZY8IsyPoBfo had no attached entries.
May 22 00:50:30 xo-ce xo-server[42654]: 2026-05-22T00:50:30.201Z xo:rest-api:error-handler INFO [GET] /backup-logs (401)
May 22 00:50:32 xo-ce xo-server[42654]: 2026-05-22T00:50:32.176Z xo:rest-api:error-handler INFO [POST] /events/5f61024f-480a-4673-aa87-1a13512804c4/subscriptions (401)
May 22 00:50:34 xo-ce xo-server[42654]: 2026-05-22T00:50:34.807Z xo:rest-api:error-handler INFO [GET] /backup-logs (401)
May 22 00:50:39 xo-ce xo-server[42654]: 2026-05-22T00:50:39.429Z xo:rest-api:error-handler INFO [POST] /events/b305b71b-1fb7-4dbd-ae1b-dd55ecf658c9/subscriptions (401)
May 22 00:50:39 xo-ce xo-server[42654]: 2026-05-22T00:50:39.530Z xo:redis WARN The id xo:token:WNSCGIpaCV0zihqsT3L3lXMkwA6XWcTgoSmzfHXT5xM had no attached entries.
May 22 00:50:44 xo-ce xo-server[42654]: 2026-05-22T00:50:44.445Z xo:rest-api:error-handler INFO [GET] /hosts (401)
May 22 00:50:44 xo-ce xo-server[42654]: 2026-05-22T00:50:44.447Z xo:rest-api:error-handler INFO [GET] /vms (401)
May 22 00:50:49 xo-ce xo-server[42654]: 2026-05-22T00:50:49.522Z xo:rest-api:error-handler INFO [POST] /events/3e83a79d-9386-4c36-801a-292734a05051/subscriptions (401)
May 22 00:50:50 xo-ce xo-server[42654]: 2026-05-22T00:50:50.730Z xo:rest-api:error-handler INFO [GET] /hosts/00fcd37d-e4c4-476e-a0ef-1ded027bebf8/alarms (401)
May 22 00:50:52 xo-ce xo-server[42654]: 2026-05-22T00:50:52.242Z xo:rest-api:error-handler INFO [POST] /events/3e83a79d-9386-4c36-801a-292734a05051/subscriptions (401)
May 22 00:52:40 xo-ce xo-server[42654]: 2026-05-22T00:52:40.784Z xo:redis WARN The id xo:token:Gy-WhZLuY-C5zmPLqx677VA9uP_v6G8_ZY8IsyPoBfo had no attached entries.
May 22 00:52:43 xo-ce xo-server[42654]: 2026-05-22T00:52:43.994Z xo:rest-api:error-handler INFO [GET] /pools/939ed551-fbd6-9868-52d8-d3997b7bf7da/stats (401)
May 22 00:52:45 xo-ce xo-server[42654]: 2026-05-22T00:52:45.872Z xo:redis WARN The id xo:token:Gy-WhZLuY-C5zmPLqx677VA9uP_v6G8_ZY8IsyPoBfo had no attached entries.
May 22 00:52:47 xo-ce xo-server[42654]: 2026-05-22T00:52:47.710Z xo:rest-api:error-handler INFO [GET] /pools/939ed551-fbd6-9868-52d8-d3997b7bf7da/stats (401)
                  MathieuRAM 1 Reply Last reply Reply Quote 0
                  • MathieuRAM Offline
                    MathieuRA Vates šŸŖ XO Team @acebmxer
                    last edited by

                    @acebmxer Thank for your investigation.

                    • You talk about a script install-xen-orchestra.sh, but the link seems dead. What is that script, it is a script provided by Vates?
                    • Bearer token is not supported (the xo doc say we can use Basic auth, or cookie to connect). If Bearer token is an absolute need, we can think about implementing it.
                    • For XO6 UI that doesn't build, can you provide the full error log?

                    To reproduce dashbloard loading issues, we have to:

                    • have a fresh XO install
                    • import an XO config that come for antoher XO
                    • connect as the default admin@admin.net, and create another user
                    • connect as the new user, and delete the default user (admin@admin.net)

                    Symptom: Every browser session token fails immediately after login. Seconds after logging in, xo-server logs

                    Only browser session that use the deleted account fails, or even sessions with untouched users?

                    After that, the issue occures even if we logout/login with the new user?

                    acebmxerA 1 Reply Last reply Reply Quote 0
                    • acebmxerA Offline
                      acebmxer @MathieuRA
                      last edited by

                      @MathieuRA

                      The script is the one i posted here - https://xcp-ng.org/forum/topic/11895/install-xo-from-sources.

                      This is what I believed caused my issues. exporting xo config into new deployed xo. Either bug in the tokens or bug in my script on how it deals with it. v5 of the ui does not show visual issue or functionality. Only v6 dashboard loading or not loading or partially loading.
                      also not sure if npm reverse proxy is any cause in the issues. as accessing xo via ip vs domain name seems to function more better but not 100%.

                      I did a fresh install and only added the pool to the new XO still with default admin@admin.net account..

                      And still having same issues. claude keep saying i have a stale toke issue. Even on a fresh build and using the default account.

                      One moment it thinks its an issue with the script next it thinks its an upstream issue.

                      If anyone else with the skills can review the code - https://github.com/acebmxer/install_xen_orchestra

                      MathieuRAM 1 Reply Last reply Reply Quote 0
                      • MathieuRAM Offline
                        MathieuRA Vates šŸŖ XO Team @acebmxer
                        last edited by

                        @acebmxer I remeber some users experiencing issues with XO6 due to a misconfigured NGINX reverse proxy (it was blocking SSE, which XO6 uses).

                        Is your reverse proxy configured correctly?

                        I won't have time to examine the script myself

                        acebmxerA 1 Reply Last reply Reply Quote 0
                        • acebmxerA Offline
                          acebmxer @MathieuRA
                          last edited by

                          @MathieuRA

                          Reverse proxy is npm. IP listed is of the new XO that was created. other then that no changes to the proxy.

                          Screenshot 2026-05-22 082629.png

                          Screenshot 2026-05-22 082706.png

                          Screenshot 2026-05-22 082853.png

                          1 Reply Last reply Reply Quote 0
                          • acebmxerA Offline
                            acebmxer
                            last edited by

                            Ok think i am making progress. I believe the stale token was a phantom issue or maybe was an issue with previous xo build, and AI just hung onto that idea. To the best of my knowledge the tokens seem to be working correctly. That is they update when i refresh or log out and log in. If i delete the token and log back it generates a new token. If i log in form a different computer it generates a new token for that login. I need to wait for the token to past its expire date/time.

                            I think to real is actual problem is with the v6 dashboard issue. Last thing need to test is build another and export this config and import into new and see if it blows up.

                            That's the first read. The two last_uses timestamps are:

                            10.100.10.131 ā†’ 1779489071582 (2026-05-22 22:31:11 UTC)
                            127.0.0.1 ā†’ 1779489074416 (2026-05-22 22:31:14 UTC)
                            Both correspond to your fresh login activity and the tcpdump capture window. Now wait ~60 seconds and run it again:

                            sudo redis-cli get xo:token:Olbs11w5o
                            If the 10.100.10.131 timestamp advances to a more recent value, the v6 UI is sending the token cookie successfully on some requests ā€” meaning the 401s on /dashboard are from a specific code path in the v6 UI that omits the cookie (upstream bug).

                            If the timestamp does not advance, the v6 UI stopped sending the cookie entirely after the initial page load ā€” which would be a cookie-scope or SameSite issue we can potentially fix on the server side.

                            āÆ sudo redis-cli get xo:token:Olbs11w5o
                            "{"client":"{}","created_at":1779488912916,"description":"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/148.0.0.0 Safari/537.36","user_id":"7e6d04ac-415e-4355-8dd6-3465467c7df1","expiration":1779524912916,"last_uses":{"10.100.10.131":{"timestamp":1779489071582},"127.0.0.1":{"timestamp":1779489074416}},"client_id":"itsdbb2c0ni"}"

                            I ran it again after refreshing the browser a few times...

                            āÆ sudo redis-cli get xo:token:Olbs11w5o

                            "{"client":"{}","created_at":1779488912916,"description":"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/148.0.0.0 Safari/537.36","user_id":"7e6d04ac-415e-4355-8dd6-3465467c7df1","expiration":1779524912916,"last_uses":{"10.100.10.131":{"timestamp":1779489677313},"127.0.0.1":{"timestamp":1779489674082}},"client_id":"itsdbb2c0ni"}"
                            The timestamps did advance:

                            10.100.10.131: 1779489071582 ā†’ 1779489677313 (+10 min)
                            127.0.0.1: 1779489074416 ā†’ 1779489674082 (+10 min)
                            So after refreshing the browser, your valid session token is being used and last_uses updates correctly. That means the v6 UI does send the cookie on most requests ā€” auth works for normal page loads and most API calls.

                            But the /dashboard (401) polling continues independently of those successful authenticated requests. That's the smoking gun: the v6 UI's dashboard widget polls /dashboard without attaching the auth cookie, even when the rest of the app is properly authenticated.

                            This is definitively an upstream XO 6 UI bug, not a problem with:

                            This install script
                            Your xo-config.cfg settings
                            The NPM reverse proxy
                            Your browser session
                            Conclusions for your situation:

                            The 401 noise is cosmetic ā€” your XO works fine, the dashboard widget just polls a route it shouldn't (or doesn't authenticate the poll).
                            Nothing in this project needs to change. The install script, config rendering, and Redis cleanup logic are all working as designed.
                            The right next step is to report it to Vates at https://github.com/vatesfr/xen-orchestra: "XO 5.201.0 web (v6) polls /rest/v0/dashboard every 31s without auth cookie even when user is logged in, producing log spam and Redis warnings."

                            1 Reply Last reply Reply Quote 0
                            • acebmxerA Offline
                              acebmxer
                              last edited by

                              Confirmed Tokens are not being stuck or orphaned. Logged in this morning the two tokens form yesterday have expired and are no longer visable. Upon login a new one was created.

                              Still v6 ui still having issues.

                              MathieuRAM 1 Reply Last reply Reply Quote 0
                              • MathieuRAM Offline
                                MathieuRA Vates šŸŖ XO Team @acebmxer
                                last edited by

                                @acebmxer Hi

                                i am able to reproduce the dashboard issue locally now, so we can also investigate on our end.

                                Can you confirm, no dashboard issue on the commit : ee53cd072304a38e8bf816dceef9bc7277b776dc?

                                acebmxerA 1 Reply Last reply Reply Quote 0
                                • acebmxerA Offline
                                  acebmxer @MathieuRA
                                  last edited by

                                  @MathieuRA said:

                                  @acebmxer Hi

                                  i am able to reproduce the dashboard issue locally now, so we can also investigate on our end.

                                  Can you confirm, no dashboard issue on the commit : ee53cd072304a38e8bf816dceef9bc7277b776dc?

                                  Current commit running - Master 5811d
                                  Current available - Master a9f85

                                  Should i update to the latest or do you have a specific build/branch to try?

                                  simonpS 1 Reply Last reply Reply Quote 0
                                  • simonpS Offline
                                    simonp Vates šŸŖ XO Team @acebmxer
                                    last edited by

                                    @acebmxer Hi,

                                    Thanks to your help we were able to identify an issue with Redis that we think is the source of the v6 dashboard loading issue.

                                    Could you try and checkout the fix_redis_encryption_issue branch, rebuild xo and restart ?

                                    This should solve the 401 issues.

                                    acebmxerA 2 Replies Last reply Reply Quote 1
                                    • acebmxerA Offline
                                      acebmxer @simonp
                                      last edited by

                                      @simonp said:

                                      @acebmxer Hi,

                                      Thanks to your help we were able to identify an issue with Redis that we think is the source of the v6 dashboard loading issue.

                                      Could you try and checkout the fix_redis_encryption_issue branch, rebuild xo and restart ?

                                      This should solve the 401 issues.

                                      Will continue to test but i think that did resolve it. I am hesitant from the logs after update. I have refreshed the page 20 times and still loads correctly no glitches.

                                      [INFO] Detected package manager: apt
[INFO] Checking for updates...
[INFO] Installed commit: fc4d34b354e3
[INFO] Remote commit:    e5210ad478b8
[INFO] New version available. Proceeding with update...
[INFO] Checking for active Xen Orchestra tasks before updating...

[INFO] Using authentication token from xo-config.cfg...
[INFO] Querying active tasks as authentication token...
[SUCCESS] No active tasks found. Proceeding with update...
[INFO] Task check performed by: authentication token
[INFO] Stopping xo-server service...
[INFO]   Preserving API token ("xo-installer")
[INFO]   Flushed browser session token (client_id y7iutpmvys7)
[INFO]   Deleted stale collection index: xo:token::indexes
[INFO]   Preserving API token ("no description")
[INFO] Flushed 1 session token(s) ā€” users will need to log in again
[INFO] Preserved 2 API token(s) ā€” third-party integrations unaffected
[INFO] Creating backup of current installation...
[SUCCESS] Backup created: /opt/xo-backups/xo-backup-20260527_094604
[INFO] Cleaning old backups (keeping 5)...
[SUCCESS] Old backups cleaned
[INFO] Pulling latest changes...
Updated 3625 paths from the index
remote: Enumerating objects: 182, done.
remote: Counting objects: 100% (91/91), done.
remote: Compressing objects: 100% (31/31), done.
remote: Total 182 (delta 63), reused 76 (delta 58), pack-reused 91 (from 1)
Receiving objects: 100% (182/182), 103.02 KiB | 6.87 MiB/s, done.
Resolving deltas: 100% (104/104), completed with 31 local objects.
From https://github.com/vatesfr/xen-orchestra
   fc4d34b35..dae64be80  master                                   -> origin/master
 + 4c172c569...d4ed13417 feat/sdn-controller/improve-startup-perf -> origin/feat/sdn-controller/improve-startup-perf  (forced update)
 * [new branch]          fix_qa_test                              -> origin/fix_qa_test
 * [new branch]          fix_redis_encryption_issue               -> origin/fix_redis_encryption_issue
 * [new branch]          lite/warning-before-leaving-XOA-deploy   -> origin/lite/warning-before-leaving-XOA-deploy
 * [new branch]          mel/acl/pool-RBAC-check                  -> origin/mel/acl/pool-RBAC-check
   2ca9e58d1..24506cfa6  mel/acls/pbds-RBAC-check                 -> origin/mel/acls/pbds-RBAC-check
 * [new branch]          refacto/migrate-to-register-rest-routes  -> origin/refacto/migrate-to-register-rest-routes
 + 761fb851c...766311798 xo6/general-tab-traffic-rule-vif         -> origin/xo6/general-tab-traffic-rule-vif  (forced update)
   de5fc9cc4..a10ed619a  xo6/traffic-rules-vif                    -> origin/xo6/traffic-rules-vif
branch 'fix_redis_encryption_issue' set up to track 'origin/fix_redis_encryption_issue'.
Switched to a new branch 'fix_redis_encryption_issue'
[INFO] Node.js v24.15.0 satisfies configured version 24 ā€” no runtime change needed
[INFO] Installing Node.js 24...
[INFO] Node.js 24 requirement satisfied (installed: v24.15.0)
[INFO] npm is available: 11.12.1
[INFO] Installing Yarn...
[INFO] Yarn is already installed: 1.22.22
[INFO] Building Xen Orchestra (this may take a while)...
[INFO] Sufficient swap space available: 4095MB
[INFO] Clearing build cache for clean rebuild...
[INFO] Moderate memory detected (5399MB RAM + 4095MB swap). Limiting build concurrency to 2.
yarn install v1.22.22
(node:87888) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
[1/5] Validating package.json...
[2/5] Resolving packages...
success Already up-to-date.
$ husky install
husky - Git hooks installed
Done in 0.57s.
yarn run v1.22.22
$ TURBO_TELEMETRY_DISABLED=1 turbo run build --filter xo-server --filter xo-server-'*' --filter xo-web --filter @xen-orchestra/web --filter @xen-orchestra/backup-archive --concurrency=2
ā•­ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā•®
ā”‚                                                                           ā”‚
ā”‚                    Update available v2.9.12 ā‰« v2.9.14                     ā”‚
ā”‚    Changelog: https://github.com/vercel/turborepo/releases/tag/v2.9.14    ā”‚
ā”‚           Run "yarn dlx @turbo/codemod@latest update" to update           ā”‚
ā”‚                                                                           ā”‚
ā”‚          Follow @turborepo for updates: https://x.com/turborepo           ā”‚
ā•°ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā•Æ
ā€¢ turbo 2.9.12
 WARNING  no caches are enabled

   ā€¢ Packages in scope: @xen-orchestra/backup-archive, @xen-orchestra/web, xo-server, xo-server-audit, xo-server-auth-github, xo-server-auth-google, xo-server-auth-ldap, xo-server-auth-oidc, xo-server-auth-saml, xo-server-backup-reports, xo-server-ipmi-sensors, xo-server-load-balancer, xo-server-netbox, xo-server-openmetrics, xo-server-perf-alert, xo-server-sdn-controller, xo-server-test-plugin, xo-server-transport-email, xo-server-transport-icinga2, xo-server-transport-nagios, xo-server-transport-slack, xo-server-transport-xmpp, xo-server-usage-report, xo-server-web-hooks, xo-web
   ā€¢ Running build in 25 packages
   ā€¢ Remote caching disabled (remote cache requested ā€” set TURBO_TOKEN and TURBO_TEAM, or run "turbo login" and "turbo link")


 Tasks:    35 successful, 35 total
Cached:    0 cached, 35 total
  Time:    48.025s 

Done in 48.47s.
[SUCCESS] Xen Orchestra built successfully
[WARNING] XO 6 web UI (@xen-orchestra/web/dist) was not built ā€” browser will use XO 5 UI at /v5.
[WARNING] This may be caused by unmet peer dependencies (pinia 3.x, vue-router 5.x).
[WARNING] Access your XO instance at: https://<host>/v5 until the upstream issue is resolved.
[INFO] Creating systemd service...
[SUCCESS] Systemd service created and enabled
[INFO] Configuring sudo for xo-service (mount/umount/findmnt)...
[SUCCESS] Sudo configured for xo-service (mount, umount, findmnt)
[INFO] Applying security hardening...
[INFO] Starting xo-server service...
[INFO] Waiting for Xen Orchestra to become ready (up to 60s)...
[INFO]   Not ready yet (attempt 1/10), retrying in 6s...
[SUCCESS] Xen Orchestra is ready (HTTPS on port 443)
[SUCCESS] Update completed successfully!
[INFO] New commit: e5210ad478b8

                                      [SUCCESS] Xen Orchestra built successfully [WARNING] XO 6 web UI (@xen-orchestra/web/dist) was not built ā€” browser will use XO 5 UI at /v5. [WARNING] This may be caused by unmet peer dependencies (pinia 3.x, vue-router 5.x). [WARNING] Access your XO instance at: https://<host>/v5 until the upstream issue is resolved.

                                      Screenshot_20260527_055115.png

                                      Screenshot_20260527_055051.png

                                      1 Reply Last reply Reply Quote 0
                                      • acebmxerA Offline
                                        acebmxer @simonp
                                        last edited by

                                        @simonp said:

                                        @acebmxer Hi,

                                        Thanks to your help we were able to identify an issue with Redis that we think is the source of the v6 dashboard loading issue.

                                        Could you try and checkout the fix_redis_encryption_issue branch, rebuild xo and restart ?

                                        This should solve the 401 issues.

                                        Switched back to Master branch and made some changes to my install script.

                                        • add diagnostics for missing XO 6 web UI build artifacts
                                        • Plain bash [[ -f ]] fails silently on unreadable paths owned by
                                          SERVICE_USER, causing false-positive missing-artifact warnings. Switch
                                          all file/dir tests and grep calls to use sudo.
                                        SUCCESS] Xen Orchestra built successfully
[INFO] Build verification passed: dist ā€” all JS chunks present.
[INFO] Build verification passed: dist ā€” all JS chunks present.
[INFO] Creating systemd service...
[SUCCESS] Systemd service created and enabled
[INFO] Configuring sudo for xo-service (mount/umount/findmnt)...
[SUCCESS] Sudo configured for xo-service (mount, umount, findmnt)
[INFO] Applying security hardening...
[INFO] Starting xo-server service...
[INFO] Waiting for Xen Orchestra to become ready (up to 60s)...
[INFO]   Not ready yet (attempt 1/10), retrying in 6s...
[SUCCESS] Xen Orchestra is ready (HTTPS on port 443)
[SUCCESS] Update completed successfully!
[INFO] New commit: 0f29421627c7

                                        v6 Dashboard still loading correctly. Thank you for the fix.

                                        1 Reply Last reply Reply Quote 0
                                        • MathieuRAM MathieuRA marked this topic as a question
                                        • MathieuRAM MathieuRA has marked this topic as solved

                                        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                                        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                                        With your input, this post could be even better šŸ’—

                                        Register Login
                                        • First post
                                          Last post