@nraynaud @olivierlambert Thanks guys!

Thanks for the tip.

I was using node v8.11.4 and had issues compiling during the upgrade then upgraded to the latest stable node version which wasn't v8.x.

I upgraded to v8.16.2 now and it runs fine. Thanks.

@nraynaud @olivierlambert Thanks guys!

@olivierlambert Thanks.
I see the problem now, it has to do with the capital extension .VHD which is the default when creating the image with disk2vhd.exe .
It works when I rename it to lowercase vhd.

This is the error when dropping in a *.VHD file.

index.js:111 Uncaught TypeError: Cannot read property 'file' of undefined
    at index.js:111
    at Array.map (<anonymous>)
    at index.js:111
    at r (patch-react.js:22)
    at g.render (ReactCompositeComponent.js:42)
    at l._renderValidatedComponentWithoutOwnerOrContext (ReactCompositeComponent.js:796)
    at l._renderValidatedComponent (ReactCompositeComponent.js:824)
    at l._updateRenderedComponent (ReactCompositeComponent.js:743)
    at l._performComponentUpdate (ReactCompositeComponent.js:721)
    at l.updateComponent (ReactCompositeComponent.js:642)

I'm running XO Community Edition xo-server 5.74.0, xo-web 5.77.0

When I drag and drop a VHD disk that is 6GB it imports fine. But when I try to drag and drop in a 97GB VHD disk it says "an error has occurred" but there are no errors in Settings -> Logs.

Is there a disk size limit when importing via the XO web interface?

Has anyone tried importing VM with XCP-ng Center 20.04.01 to XCP-ng 8.2? I'm getting 1Mbps transfer speed.

When I connect the same XCP-ng Center 20.04.01 instance to XCP-ng 8.0 and do an import I get 100Mbps transfer speed.

Anyone can help?

I suspect the slow upload during import is related to this... https://xcp-ng.org/forum/post/34970 ?

I see that installing XCP-ng 8.2.0 will create ext4 storage repositories by default. Why isn't dom0 also ext4?

Filesystem Type Size Used Avail Use% Mounted on
/dev/sda1 ext3 18G 2.2G 15G 13% /
/dev/sda5 ext3 3.9G 20M 3.6G 1% /var/log

@olivierlambert Will connecting with http://<IP> authenticate using plain text l/p over the network?

@julien-f Actually it'll be good to know how to set that parameter as a service but it is not necessary anymore. The better solution was to enable TLSv1.2 on the directory instead.

Thanks for the help.

@julien-f Thanks for the help.

My xo-server is installed in /opt/xen-orchestra/packages/xo-server/bin/xo-server.

After stopping the service when I run

node --tls-min-v1.0 /opt/xen-orchestra/packages/xo-server/bin/xo-server

I get the error

2020-07-06T00:58:51.959Z xo:plugin INFO Cannot find module '/usr/local/lib/node_modules/xo-server-cloud'
Require stack:
- /opt/xen-orchestra/packages/xo-server/dist/index.js
- /opt/xen-orchestra/packages/xo-server/index.js
- /opt/xen-orchestra/packages/xo-server/bin/xo-server {
  error: Error: Cannot find module '/usr/local/lib/node_modules/xo-server-cloud'

How do I add the --tls-min-v1.0 parameter in and start it as a service instead?

After upgrading to node.js v12.18.2 and upgrading to the latest version of XO Community 5.62.0. I'm getting an error with the auth-ldap plugin connecting to Active Directory over SSL port 636.

140338573449088:error:1425F102:SSL routines:ssl_choose_client_version:unsupported protocol:../deps/openssl/openssl/ssl/statem/statem_lib.c:1942:

I'm currently guessing it has something to do with node 12 defaults to TLS 1.2. And need to add --tls-min-v1.0 when running XO.
How do I add this to test it?

I got the idea from here: https://stackoverflow.com/questions/59898050/axios-ssl-error-with-node-12-ssl-routinesssl-choose-client-versionunsupporte

Thanks for the tip.

I was using node v8.11.4 and had issues compiling during the upgrade then upgraded to the latest stable node version which wasn't v8.x.

I upgraded to v8.16.2 now and it runs fine. Thanks.