Just as an addition, as I still had it with current code from main and found out what is going on.
The cause can simply be a wrong time on the XO Server.
The fix here simply extends the time drift, but if your server is more out of sync than this value, you will always see the error:
https://github.com/vatesfr/xen-orchestra/pull/9681/changes
Can be made more visible in code with this change:
File: xen-orchestra/@xen-orchestra/web-core/lib/packages/remote-resource/sse.store.ts
//const hasErrorSse = computed(() => isError.value || sse.value.errorSse !== null)
const hasErrorSse = computed(() => {
const result = isError.value || sse.value.errorSse !== null
if (result) {
console.error('[XO SSE STATE]', {
isError: isError.value,
lastPing: sse.value.lastPing,
now: now.value.getTime(),
difference: sse.value.lastPing
? now.value.getTime() - sse.value.lastPing
: null,
errorSse: sse.value.errorSse,
})
}
return result
})
const isConnected = computed(() => sse.value.id !== undefined)