Hi everyone just tested and the install went smooth no problems... test network is the problem being blocked... thank you for all the help

Okay after running the script this is what happened:

root@xenorc:/opt# sudo curl https://raw.githubusercontent.com/scottalanmiller/xenorchestra_installer/master/xo_install.sh | bash
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 1146 100 1146 0 0 604 0 0:00:01 0:00:01 --:--:-- 604
Reading package lists... Done
Building dependency tree
Reading state information... Done
nfs-common is already the newest version (1:1.2.8-9.2ubuntu1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Installing the NodeSource Node.js v6.x repo...

Populating apt-get cache...

• apt-get update
  Get:1 http://security.ubuntu.com/ubuntu yakkety-security InRelease [102 kB]
  Hit:2 http://za.archive.ubuntu.com/ubuntu yakkety InRelease
  Get:3 http://za.archive.ubuntu.com/ubuntu yakkety-updates InRelease [102 kB]
  Hit:4 https://deb.nodesource.com/node_6.x yakkety InRelease
  Get:5 http://za.archive.ubuntu.com/ubuntu yakkety-backports InRelease [102 kB]
  Get:6 http://za.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 Packages [146 kB]
  Get:7 http://za.archive.ubuntu.com/ubuntu yakkety-updates/main i386 Packages [144 kB]
  Get:8 http://za.archive.ubuntu.com/ubuntu yakkety-updates/universe i386 Packages [76.0 kB]
  Get:9 http://za.archive.ubuntu.com/ubuntu yakkety-updates/universe amd64 Packages [78.4 kB]
  Fetched 752 kB in 1s (392 kB/s)
  Reading package lists... Done

Confirming "yakkety" is supported...

• curl -sLf -o /dev/null 'https://deb.nodesource.com/node_6.x/dists/yakkety/Release'

Adding the NodeSource signing key to your keyring...

• curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | apt-key add -
  OK

Creating apt sources list file for the NodeSource Node.js v6.x repo...

• echo 'deb https://deb.nodesource.com/node_6.x yakkety main' > /etc/apt/sources.list.d/nodesource.list
• echo 'deb-src https://deb.nodesource.com/node_6.x yakkety main' >> /etc/apt/sources.list.d/nodesource.list

Running apt-get update for you...

• apt-get update
  Hit:1 http://za.archive.ubuntu.com/ubuntu yakkety InRelease
  Hit:2 http://za.archive.ubuntu.com/ubuntu yakkety-updates InRelease
  Hit:3 http://za.archive.ubuntu.com/ubuntu yakkety-backports InRelease
  Hit:4 http://security.ubuntu.com/ubuntu yakkety-security InRelease
  Hit:5 https://deb.nodesource.com/node_6.x yakkety InRelease
  Reading package lists... Done

Run apt-get install nodejs (as root) to install Node.js v6.x and npm

Reading package lists... Done
Building dependency tree
Reading state information... Done
nodejs is already the newest version (6.9.4-1nodesource1~yakkety1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 15245 100 15245 0 0 7949 0 0:00:01 0:00:01 --:--:-- 7948
Reading package lists... Done
Building dependency tree
Reading state information... Done
build-essential is already the newest version (12.1ubuntu2).
git is already the newest version (1:2.9.3-1).
libpng-dev is already the newest version (1.6.25-1).
python-minimal is already the newest version (2.7.11-2).
redis-server is already the newest version (2:3.2.1-1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Cloning into 'xo-server'...
remote: Counting objects: 10478, done.
remote: Compressing objects: 100% (59/59), done.
remote: Total 10478 (delta 31), reused 0 (delta 0), pack-reused 10419
Receiving objects: 100% (10478/10478), 2.71 MiB | 1.11 MiB/s, done.
Resolving deltas: 100% (7503/7503), done.
Checking connectivity... done.
Cloning into 'xo-web'...
remote: Counting objects: 26050, done.
remote: Compressing objects: 100% (11/11), done.
error: RPC failed; curl 56 GnuTLS recv error (-54): Error in the pull function.
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
npm WARN prefer global [email protected] should be installed with -g
npm WARN prefer global [email protected] should be installed with -g
npm WARN prefer global [email protected] should be installed with -g
npm WARN prefer global [email protected] should be installed with -g

[email protected] install /opt/xo-server/node_modules/argon2
node-gyp rebuild

make: Entering directory '/opt/xo-server/node_modules/argon2/build'
CC(target) Release/obj.target/libargon2/argon2/src/opt.o
CC(target) Release/obj.target/libargon2/argon2/src/argon2.o
CC(target) Release/obj.target/libargon2/argon2/src/core.o
CC(target) Release/obj.target/libargon2/argon2/src/blake2/blake2b.o
CC(target) Release/obj.target/libargon2/argon2/src/thread.o
CC(target) Release/obj.target/libargon2/argon2/src/encoding.o
AR(target) Release/obj.target/argon2.a
COPY Release/argon2.a
CXX(target) Release/obj.target/argon2/src/argon2_node.o
SOLINK_MODULE(target) Release/obj.target/argon2.node
COPY Release/argon2.node
make: Leaving directory '/opt/xo-server/node_modules/argon2/build'

[email protected] install /opt/xo-server/node_modules/bcrypt
node-pre-gyp install --fallback-to-build

bash: line 13: 3533 Killed sudo npm install
bash: line 16: cd: /opt/xo-web: No such file or directory
node-pre-gyp ERR! Tried to download(404): https://github.com/kelektiv/node.bcrypt.js/releases/download/v1.0.2/bcrypt_lib-v1.0.2-node-v51-linux-x64.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for [email protected] and [email protected] (node-v51 ABI) (falling back to source compile with node-gyp)
make: Entering directory '/opt/xo-server/node_modules/bcrypt/build'shing
CXX(target) Release/obj.target/bcrypt_lib/src/blowfish.o
CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt.o
CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt_node.osIntoIdealTree
SOLINK_MODULE(target) Release/obj.target/bcrypt_lib.nodeDepsIntoIdealTree
COPY Release/bcrypt_lib.node
COPY /opt/xo-server/node_modules/bcrypt/lib/binding/bcrypt_lib.node
TOUCH Release/obj.target/action_after_build.stamp
make: Leaving directory '/opt/xo-server/node_modules/bcrypt/build'
npm WARN prepublish-on-install As of npm@5, prepublish scripts will run only for npm publish.
npm WARN prepublish-on-install (In npm@4 and previous versions, it also runs for npm install.)
npm WARN prepublish-on-install See the deprecation note in npm help scripts for more information.
npm WARN lifecycle [email protected]~prepublish: cannot run in wd %s %s (wd=%s) [email protected] npm run build /opt/xo-server
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

[email protected] prebuild /opt/xo-server
index-modules src/api src/xapi/mixins src/xo-mixins

index generated src/api/index.js
index generated src/xo-mixins/index.js
index generated src/xapi/mixins/index.js

[email protected] build /opt/xo-server
gulp build --production

[15:34:46] Using gulpfile /opt/xo-server/gulpfile.js
[15:34:46] Starting 'build'...
[15:34:46] Starting 'clean'...
[15:34:46] Finished 'clean' after 8.5 ms
[15:34:46] Starting 'buildCoffee'...
[15:34:46] Starting 'buildEs6'...
[15:34:53] Finished 'buildCoffee' after 6.68 s
[15:35:33] Finished 'buildEs6' after 47 s
[15:35:33] Finished 'build' after 47 s
root@xenorc:/opt#

@Danp I am going to run :

git clone -b stable https://github.com/vatesfr/xo-web
sudo cp sample.config.yaml .xo-server.yaml
sudo sed -i /mounts/a\" '/': '/opt/xo-web/dist'" .xo-server.yaml
cd /opt/xo-web
sudo npm install
sudo npm run build

since that is where it stopped?

@olivier thank you will check it out

Hi everyone just tested and the install went smooth no problems... test network is the problem being blocked... thank you for all the help

@olivier Okay will test the install script now on a spare Jessie server, looks already a lot better no warning so far wit npm install in the xo-server dir :D. How does the costing work for XOA?

@olivier But I will be stuck on my home network when I try installing again from the script? Unless its something on this network causing problems...

@olivier How long is the trial?

@olivier First time Xen user wanted to have the full experience and see what all I can do with Xen and maybe replace my Vmware server at home...

@olivier I think you might be right, I am on the test network and I dont really mess with the network admins config on the main router its quite a big network... Will try to install Orchastra on the main network and see maybe you are right...

I allocated 4gb of ram to the vm....

After opening the firewall and git config --global url."https://".insteadOf git://

This is now my error :

root@xenorc:/opt/xo-web# sudo npm install
Killed ............] \ fetchMetadata: sill mapToRegistry uri https://registry.npmjs.org/xo-lib

@Dashrender Okay must I run:
git fetch -a origin (git://github.com/fizzed/font-mfizz.git)
git fetch -a origin (git://github.com/gulpjs/gulp.git)

but after that I need to rerun npm install then it will bomb out again?

@travisdh1 I have no idea.... network connection is fine...