Will do. I've got an installation of it in two locations and neither are behind a proxy.

In a moment of early-onset senility/dementia I confused npm with dnf - somehow! So there's obviously a chance I'm doing something incorrectly.

Has anyone else seen this error? I was working in the XOA VM/web interface and, well, got these messages:

12/5/2019, 2:49:34 PM: xoa-updater may be run again to upgrade packages
12/5/2019, 2:51:15 PM: Start upgrading
12/5/2019, 2:51:15 PM: stable selected
12/5/2019, 2:51:15 PM: New versions available:
12/5/2019, 2:51:16 PM:   xoa-updater 0.23.1
12/5/2019, 2:51:16 PM: Downloading packages...
12/5/2019, 2:51:23 PM:   xoa-updater ............................................................................................................................................................................................................................................................................. ok ✔
12/5/2019, 2:51:23 PM: Saving current updater version in /usr/local/lib/node_modules/xoa-updater/dist-1575579083239 ...ok ✔
12/5/2019, 2:51:23 PM: Installing packages...
12/5/2019, 2:51:27 PM: Command failed: npm uninstall -g --silent xoa-updater

I should note that I'm running xo-server 5.50.1 and xo-web 5.50.3 and this setup has been working fine. It was an upgrade/switch from XenServer 7.6.

Is it odd that this is trying to run "npm" when the underlying OS for Xen Orchestra seems to be Debian? I thought npm was on Red Hat/CentOS distros. (I could easily be off on an irrelevant tangent here.)

When I ssh to the Xen Orchestra VM:

Build number: 19.06.24

Based on Debian GNU/Linux 9 (Stable) 64bits in PVHVM mode