Error: unable to determine NODE_VERSION automatically

Hello Everybody.
I’m trying to install from scratch a node on a VPS.
I use the script made by @LaMat
I have the following error. Do you know what is the problem and how can I solve it ?
Thank you very much !

I updated the installation and script and it should now work for you, try again.

Why the issue happens:

The script tries to determine the latest node version automatically via this snippet:

NODE_VERSION=$(curl -s https://releases.quilibrium.com/release | grep -E "^node-[0-9]+(\.[0-9]+)*" | grep -v "dgst" | sed 's/^node-//' | cut -d '-' -f 1 | head -n 1)

If it fails to do so, either because it can’t connect to https://releases.quilibrium.com/release or for some other reasons, then it gives you that error.

In that case, you will have to install manually.

Now, you will probably be able to install. Because to install, we don’t actually need to determine the latest node version.

But when you use the update script on that same machine, you will likely hit the same error. Because for updating, we do need to know the latest node version.

Script is here if anyone has suggestions:

Install

Update

1 Like

Thank you very much for your answer. I’ll try it when back home and let you know if it works. Thanks

Hello @LaMat

I tried the updated installation script.

It seems that it cannot connect to releases.quilibrium.com.

Do you know what may be the problem ?

I finally tried to install the node manually step by step following https://quilibrium.guide/setup-node/

I have an error at this stage when installing the node

echo "4. creating client folder, and downloading qclient binary..."
mkdir client && cd client
echo "... client folder created"
files=$(curl https://releases.quilibrium.com/qclient-release | grep $release_os-$release_arch)
for file in $files; do
    qclient_version=$(echo "$file" | cut -d '-' -f 2)
    if ! test -f "./$file"; then
        curl "https://releases.quilibrium.com/$file" > "$file"
        echo "... downloaded $file"
    fi
done
mv qclient-$qclient_version-$release_os-$release_arch qclient
chmod +x ./qclient
echo "... \"qclient-$qclient_version-$release_os-$release_arch\" renamed to \"qclient\""
cd ..
echo "... download of required qclient files done"

Question : is it still possible to run new nodes? The signature files seem missing from the repo ?

IMO the issue is in your machine or your hosting provider.
I can install nodes normally via the script.

Try to ping

curl -I https://releases.quilibrium.com/

and see if the machine can connect to that URL

If it can’t, that is the issue.

In that case, you can try this method to run your node

But first be sure that the node files have been downloaded, there should be a /root/ceremonyclient folder in your machine.

BTW, who is your hosting provider.? Another user reported the same issue last week. I think they were on Contabo, and they blocked access to quilibrium.com in the past.

I also discovered that many times there is a very quick fix to that error: just restart your node (option 7 in the menu)

Hello @LaMat
First of all, thank you for your support.
Then, the command curl did not worked. Cant connect.
And then I tried the “Running the node via binary file”.
Here is the error I have now:

I dont have the file in the node rep.

And my service provider is CONTABO

You don’t have the binary file of the node. It wasn’t downloaded.
And yes, CONTABO is almost always the culprit.

I suggest you choose a better server provider, here is my top list: Best server providers | Quilibrium.one

Go with dedicated, not a VPS.


If this is a fresh node and you don’t have keys to save, you could delete the node folder

rm -r /root/ceremonyclient

and then git pull again

cd
git clone https://github.com/QuilibriumNetwork/ceremonyclient.git

Then try to start again the service

sudo systemctl daemon-reload
sudo systemctl enable ceremonyclient
sudo service ceremonyclient start

Problem solved.

The solution is here if there is anoter person in my case (solution provided by “Gorilla DONG” on the discord):

you modify your nameserver
/etc/resolv.conf
nameserver 8.8.8.8

:smiley:

1 Like