I do not see any logs or admin panel that insinuates that it is actively being blocked.

OMG, it is somehow Cloudflare zero trust access.

We have our XOA behind ZT, so on a whim I tried importing the vm export directly in our internal network, and it works.

Sorry for the goose chase, maybe this will help someone in the future. May update this when we have some better idea of what the problem actually is.

@olivierlambert

$ node --version
v18.17.1

@olivierlambert Done, no change in behaviour. Still nothing in Tasks or Logs pages.

@Danp

Recently

Hello!

I have done some searching for this issue, if I have missed it I am very sorry!

I am attempting to have an offline, encrypted backup of a vm. This vm will only be brought online in the rare event it is needed. I have created an xva export, however when I attempt to import nothing happens.

It takes a couple minues, and then I see the upload traffic on my end, but nothing happens on xoa and then it times out after 10 minutes.

This is the only error I see in xo-server. I do not see anything in tasks or logs in xoa.

Sep 12 16:55:51 xoa xo-server[1009]: 2023-09-12T16:55:51.839Z xo:xo ERROR HTTP request error {
Sep 12 16:55:51 xoa xo-server[1009]:   data: { filter: undefined, limit: undefined },
Sep 12 16:55:51 xoa xo-server[1009]:   error: NodeError: Premature close
Sep 12 16:55:51 xoa xo-server[1009]:       at ServerResponse.onclose (/opt/xen-orchestra/packages/xo-server/node_modules/readable-stream/lib/internal/streams/end-of-stream.js:121:76)
Sep 12 16:55:51 xoa xo-server[1009]:       at ServerResponse.emit (node:events:526:35)
Sep 12 16:55:51 xoa xo-server[1009]:       at ServerResponse.patchedEmit [as emit] (/opt/xen-orchestra/@xen-orchestra/log/configure.js:52:17)
Sep 12 16:55:51 xoa xo-server[1009]:       at emitCloseNT (node:_http_server:996:10)
Sep 12 16:55:51 xoa xo-server[1009]:       at Socket.onServerResponseClose (node:_http_server:278:5)
Sep 12 16:55:51 xoa xo-server[1009]:       at Socket.emit (node:events:526:35)
Sep 12 16:55:51 xoa xo-server[1009]:       at Socket.patchedEmit [as emit] (/opt/xen-orchestra/@xen-orchestra/log/configure.js:52:17)
Sep 12 16:55:51 xoa xo-server[1009]:       at TCP.<anonymous> (node:net:323:12)
Sep 12 16:55:51 xoa xo-server[1009]:       at TCP.callbackTrampoline (node:internal/async_hooks:130:17),
Sep 12 16:55:51 xoa xo-server[1009]:   fn: 'handleGetAllObjects'
Sep 12 16:55:51 xoa xo-server[1009]: }
lines 2056458-2056529/2056529 (END)

@olivierlambert said in How to kubernetes on xcp-ng (csi?):

To help k8s integration with XCP-ng/XO we already have plans to write a Node driver for Rancher.

OMG that would be amazing!