I already have an @unikname so I skipped this part. But for information : my @unikname is an individual one.
My server is a Debian 9.11 (stretch) on OVH servers. There is not much app installed : apache2 and docker. So it’s like a fresh server, perfect to test installation of a node !
I downloaded the uns with the command :
cd /opt/ mkdir uns cd uns wget https://unikname-cli-assets.s3.fr-par.scw.cloud/uns-linux-x64.tar.gz tar xvf uns-linux-x64.tar.gz cd uns/bin ./uns
The installation seems to be perfect :
UNS.network CLI VERSION @uns/cli/3.2.0 linux-x64 node-v12.16.1 USAGE $ uns [COMMAND] COMMANDS autocomplete display autocomplete installation instructions cryptoaccount Manage Crypto Account (`uns cryptoaccount` to display Crypto Account commands) delegate Manage UNS delegates (`uns delegate` to display Delegate commands) help display help for uns properties Manage UNIK properties (`uns properties` to display UNIK properties commands) resolve Resolve a decentralized identifier. send Send owned UNS protocol tokens to another wallet. status Display blockchain status unik Manage UNIK (`uns unik` to display UNIK commands) update update the uns CLI version UNS CLI Version
Registering as a delegate
Now, it’s time to register. I use this command :
$> ./uns unik:disclose "@atouk" -e "atouk" ./uns : ligne 45 : 30265 Instruction non permise "$NODE" "$DIR/run" "$@"
It seems that the uns.cli uses NodeJS, so I installed it with
$> apt-get update && apt-get install curl $> curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash - $> apt-get install -y nodejs
But it was not the problem. Node seems to be embed with uns.cli. So I used the command at the line 45 :
?> /opt/uns/uns/bin/node /opt/uns/uns/bin/run unik:disclose @atouk -e atouk  3288 illegal hardware instruction /opt/uns/uns/bin/node /opt/uns/uns/bin/run unik:disclose @atouk -e atouk
I downloaded 64-bits tarball because of of my CPU architecture, but it seems that something goes wrong anyway.
I’ll update this thread if i find the solution.
See you later.