Topics created by Pechkin000

@Pechkin000 It should be installed alongside xo-server, it depends how you installed XO on this.

But still, it requires root access for security.

Hi Pechkin000,

Try this :

npm install url-loader

yarn install v1.22.11
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
info fsevents@2.3.2: The platform "linux" is incompatible with this module.
info "fsevents@2.3.2" is an optional dependency and failed compatibility check. Excluding it from installation.
info fsevents@1.2.13: The platform "linux" is incompatible with this module.
info "fsevents@1.2.13" is an optional dependency and failed compatibility check. Excluding it from installation.
[4/5] Linking dependencies...
[5/5] Building fresh packages...
Done in 22.66s.

I have isolated the problem. The issue was with dynamic memory allocation on our test server. This was definitely a localized issue.
Cheers

@luiscamaral Let me reply to myself. If you update xoa it will show user and password as in bellow description:

Template for Alpine Linux 3.10, with 'root' username and 'xohub' password, DHCP enabled
😊

In case someone ran into the same problem here is how I solved it.
I had a feeling this was http mounts issue. I checked and looks like during update process the .xo-server.toml got deleted. I copied the sample one from the /opt/xen-orchestra/packages/xo-server/sample.config.toml , edited the http.mount and bob's your uncle.

I have a feeling this has something to do with the format of that file change. When I originally built from source the file has a slightly different syntax and it was called .xo-server.yaml. At least according tot he directions I used to build. In any case its all back to normal now.
Thanks you everyone for your help.

I'm fed up with trolling. I already explained that XOA can be seen as a "Xen Orchestra dedicated distro", we make the choice to build it from a "snapshot" (commit) on various component. It's not based on a GitHub branch. That's our choice that you can do on your side if you want to build a XOA equivalent. You have all the 3 liberties of GPL software because everything is available on GitHub.

XOA is a choice of which version to use together for each component, with QA and mastered env to be able to make efficient support.

If you can't understand that despite 3 or 4 persons explained that to you, we can't do anything else. Good bye.