🛰️ XO 6: dedicated thread for all your feedback!

[acebmxer]

@Baronvaile

Just to confirm this is with actual XOA and not XO from sources? Have you rebooted XO? Check logs? sudo journalctl -u xo-server -n 50

Edit - Just updated my home lab XOA

I see same thing... XO from sources no issues. Work XOA no issues...

[ph7]

@Baronvaile
Started my 6.4.0 test VM and got the same

[ph7]

My is XOA

[acebmxer]

I am seeing these errors....

[09:45 30] xoa@xoa:~$ sudo journalctl -u xo-server -p warning --no-pager
Mar 13 13:13:52 xoa systemd[1]: xo-server.service: State 'stop-sigterm' timed out. Killing.
Mar 13 13:13:52 xoa systemd[1]: xo-server.service: Main process exited, code=killed, status=9/KILL
Mar 13 13:13:52 xoa systemd[1]: xo-server.service: Failed with result 'timeout'.
-- Boot 8398ef48e4e94d27b11bfc3300a68727 --
Apr 25 11:37:14 xoa systemd[1]: xo-server.service: State 'stop-sigterm' timed out. Killing.
Apr 25 11:37:14 xoa systemd[1]: xo-server.service: Main process exited, code=killed, status=9/KILL
Apr 25 11:37:14 xoa systemd[1]: xo-server.service: Failed with result 'timeout'.
-- Boot 9a9a6f09bdea43729cbe3aa74acc7a3b --
Apr 30 09:36:06 xoa systemd[1]: xo-server.service: State 'stop-sigterm' timed out. Killing.
Apr 30 09:36:06 xoa systemd[1]: xo-server.service: Main process exited, code=killed, status=9/KILL
Apr 30 09:36:06 xoa systemd[1]: xo-server.service: Failed with result 'timeout'.
[09:45 30] xoa@xoa:~$ sudo journalctl -u xo-server -f
Apr 30 09:43:14 xoa xo-server[594]:       at Function.emit (node:events:519:28)
Apr 30 09:43:14 xoa xo-server[594]:       at Function.emit (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/log/configure.js:52:17)
Apr 30 09:43:14 xoa xo-server[594]:       at Server.<anonymous> (file:///usr/local/lib/node_modules/xo-server/src/index.mjs:977:13)
Apr 30 09:43:14 xoa xo-server[594]:       at Server.emit (node:events:531:35)
Apr 30 09:43:14 xoa xo-server[594]:       at Server.patchedEmit [as emit] (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/log/configure.js:52:17)
Apr 30 09:43:14 xoa xo-server[594]:       at onParserExecuteCommon (node:_http_server:977:14)
Apr 30 09:43:14 xoa xo-server[594]:       at onParserExecute (node:_http_server:881:3) {
Apr 30 09:43:14 xoa xo-server[594]:     code: 'DEP0060'
Apr 30 09:43:14 xoa xo-server[594]:   }
Apr 30 09:43:14 xoa xo-server[594]: }

[Baronvaile]

@acebmxer Correct, this is with XOA. While watching the journalctl and launching XOA in chrome, I get this output.

[ph7]

[17:00 30] xoa@xoa:~$ sudo journalctl -u xo-server -f
Apr 30 16:23:13 xoa xo-server[569]: 2026-04-30T14:23:13.264Z xo:main INFO Setting up / → /usr/local/lib/node_modules/@xen-orchestra/web/dist
Apr 30 16:26:27 xoa xo-server[569]: 2026-04-30T14:26:27.942Z xo:rest-api:error-handler INFO [GET] /users/370331c9-fe77-49db-b2a0-e38f776607bd (403)
Apr 30 16:26:28 xoa xo-server[569]: 2026-04-30T14:26:28.549Z xo:rest-api:error-handler INFO [GET] /pools (403)
Apr 30 16:26:28 xoa xo-server[569]: 2026-04-30T14:26:28.555Z xo:rest-api:error-handler INFO [GET] /hosts (403)
Apr 30 16:26:28 xoa xo-server[569]: 2026-04-30T14:26:28.563Z xo:rest-api:error-handler INFO [GET] /vms (403)
Apr 30 16:26:28 xoa xo-server[569]: 2026-04-30T14:26:28.627Z xo:rest-api:error-handler INFO [GET] /tasks (403)
Apr 30 16:26:28 xoa xo-server[569]: 2026-04-30T14:26:28.812Z xo:rest-api:error-handler INFO [GET] /alarms (403)
Apr 30 16:26:28 xoa xo-server[569]: 2026-04-30T14:26:28.812Z xo:rest-api:error-handler INFO [GET] /vm-controllers (403)
Apr 30 16:26:28 xoa xo-server[569]: 2026-04-30T14:26:28.813Z xo:rest-api:error-handler INFO [GET] /vdis (403)
Apr 30 16:26:28 xoa xo-server[569]: 2026-04-30T14:26:28.813Z xo:rest-api:error-handler INFO [GET] /srs (403)

[acebmxer]

I didnt refresh the page when i ran the blow command before.

xoa@xoa:~$ sudo journalctl -u xo-server -f
Apr 30 10:28:02 xoa xo-server[568]:     at new Promise (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/promise.js:103:10)
Apr 30 10:28:02 xoa xo-server[568]:     at Peer.request (/usr/local/lib/node_modules/xo-server-xoa/node_modules/json-rpc-peer/src/index.js:139:12)
Apr 30 10:28:02 xoa xo-server[568]:     at JsonRpcWebSocketClient.call (/usr/local/lib/node_modules/xo-server-xoa/node_modules/jsonrpc-websocket-client/src/index.js:63:23)
Apr 30 10:28:02 xoa xo-server[568]:     at Xoa.apply [as _getCurrentChannel] (/usr/local/lib/node_modules/xo-server-xoa/src/index.js:704:45)
Apr 30 10:28:02 xoa xo-server[568]:     at Xo.<anonymous> (file:///usr/local/lib/node_modules/xo-server/src/xo.mjs:256:24)
Apr 30 10:28:02 xoa xo-server[568]:     at Config.getGuiRoutes (file:///usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/mixins/Config.mjs:102:52)
Apr 30 10:28:02 xoa xo-server[568]:     at main (file:///usr/local/lib/node_modules/xo-server/src/index.mjs:1037:56)
Apr 30 10:28:02 xoa xo-server[568]: 2026-04-30T15:28:02.981Z xo:main INFO Setting up /v5 → /usr/local/lib/node_modules/xo-web/dist
Apr 30 10:28:02 xoa xo-server[568]: 2026-04-30T15:28:02.981Z xo:main INFO Setting up /v6 → /usr/local/lib/node_modules/@xen-orchestra/web/dist
Apr 30 10:28:02 xoa xo-server[568]: 2026-04-30T15:28:02.981Z xo:main INFO Setting up / → /usr/local/lib/node_modules/@xen-orchestra/web/dist
Apr 30 10:29:00 xoa xo-server[568]: 2026-04-30T15:29:00.487Z xo:rest-api:error-handler INFO [GET] /users/f1397281-6d64-442b-a78c-e53fea09aa76 (403)
Apr 30 10:29:01 xoa xo-server[568]: 2026-04-30T15:29:01.014Z xo:rest-api:error-handler INFO [GET] /pools (403)
Apr 30 10:29:01 xoa xo-server[568]: 2026-04-30T15:29:01.020Z xo:rest-api:error-handler INFO [GET] /hosts (403)
Apr 30 10:29:01 xoa xo-server[568]: 2026-04-30T15:29:01.027Z xo:rest-api:error-handler INFO [GET] /vms (403)
Apr 30 10:29:01 xoa xo-server[568]: 2026-04-30T15:29:01.044Z xo:rest-api:error-handler INFO [GET] /tasks (403)
Apr 30 10:29:01 xoa xo-server[568]: 2026-04-30T15:29:01.077Z xo:rest-api:error-handler INFO [GET] /alarms (403)
Apr 30 10:29:01 xoa xo-server[568]: 2026-04-30T15:29:01.079Z xo:rest-api:error-handler INFO [GET] /vm-controllers (403)
Apr 30 10:29:01 xoa xo-server[568]: 2026-04-30T15:29:01.082Z xo:rest-api:error-handler INFO [GET] /vdis (403)
Apr 30 10:29:01 xoa xo-server[568]: 2026-04-30T15:29:01.088Z xo:rest-api:error-handler INFO [GET] /srs (403)
Apr 30 10:29:13 xoa xo-server[568]: 2026-04-30T15:29:13.204Z xo:rest-api:error-handler INFO [GET] /users/f1397281-6d64-442b-a78c-e53fea09aa76 (403)
Apr 30 10:29:13 xoa xo-server[568]: 2026-04-30T15:29:13.748Z xo:rest-api:error-handler INFO [GET] /alarms (403)
Apr 30 10:29:13 xoa xo-server[568]: 2026-04-30T15:29:13.751Z xo:rest-api:error-handler INFO [GET] /vm-controllers (403)
Apr 30 10:29:13 xoa xo-server[568]: 2026-04-30T15:29:13.751Z xo:rest-api:error-handler INFO [GET] /srs (403)
Apr 30 10:29:13 xoa xo-server[568]: 2026-04-30T15:29:13.751Z xo:rest-api:error-handler INFO [GET] /vdis (403)
Apr 30 10:29:13 xoa xo-server[568]: 2026-04-30T15:29:13.753Z xo:rest-api:error-handler INFO [GET] /pools (403)
Apr 30 10:29:13 xoa xo-server[568]: 2026-04-30T15:29:13.778Z xo:rest-api:error-handler INFO [GET] /hosts (403)
Apr 30 10:29:13 xoa xo-server[568]: 2026-04-30T15:29:13.778Z xo:rest-api:error-handler INFO [GET] /vms (403)
Apr 30 10:29:13 xoa xo-server[568]: 2026-04-30T15:29:13.784Z xo:rest-api:error-handler INFO [GET] /tasks (403)

[MathieuRA]

Hello, I'm investigating the problem.

[MathieuRA]

Can someone open a support tunnel, so that i can test a fix?

PR: https://github.com/vatesfr/xen-orchestra/pull/9798

MathieuRA opened this pull request in vatesfr/xen-orchestra

closed fix(rest-api): early return for admin user in acl check #9798

[Baronvaile]

@MathieuRA

[MathieuRA]

Thanks @Baronvaile. Can i restart xo-server?

[Baronvaile]

Sorry, I was out for a bit. Yes, you can restart my xoa.

[acebmxer]

@MathieuRA

If you still are waiting i have opened a support tunnel - 35965 this is for my home lab. You may reboot XOA if needed.

[MathieuRA]

Thanks @Baronvaile, the fix seems to work.

@acebmxer i will also patch your XOA, It's better to have several confirmations

[Baronvaile]

Can confirm that XOA v6 looks good now.

[MathieuRA]

@acebmxer It also works on your XOA.

Thank you both for your availability for testing. I will see with the XO team when to release a fix.

We apologize for any inconvenience

[Baronvaile]

@MathieuRA Thank you for the team's and specifically your dedication to the project and the quick turn around time.

[acebmxer]

@MathieuRA

Confirmed Dashboard now loads correctly.

[poddingue]

@Baronvaile said:

After upgrading from 6.3.3 to the new 6.4.0 release, the dashboard page for xoa 6 is just spinning. v5 seem unaffected after the update. I have restarted the xoa vm. The xoa-updated show all up to date and xoa check shows healthy.

Thanks for the detailed report and the journalctl output, and to @acebmxer and @ph7 for the confirmations. I've filed this upstream as GitHub issue #9799 so the dev team can track it properly. The in-thread fix from @mathieura got your instances running again, but the root cause is worth investigating so it doesn't come back in a future update. I'll update the issue if anything changes on that front.

[poddingue]

@probain said:

probain said:

Unfortunately, commit https://github.com/vatesfr/xen-orchestra/pull/9727 doesn't fix this issue of the VM-console reloading constantly. With loss of focus as a result. At least not on XO6..

PR #9727 was supposed to fix this but it sounds like the problem is still there on XO 6 for you. I've filed it as GitHub issue #9800 so the team can take another look with fresh eyes. If you have any more details about when the reload triggers (for example, whether it happens more on certain browsers or VM types) adding them to the issue would probably help narrow it down.

pierre-briffaux opened this pull request in vatesfr/xen-orchestra

closed fix(vm/console): fix VNC reconnection causing focus loss #9727