Installation from Debian Package (manual) NOT generating configuration files

[theVasilis]

Dear team

I'm using the GitHub guide and this command: sudo wget -O /var/cache/apt/archives/dvpn-node-manager_latest.deb https://github.com/sentinelgrowthdao/dvpn-node-manager/releases/download/v1.0.0-alpha10/dvpn-node-manager_1.0.0-alpha10_$(dpkg --print-architecture).deb && sudo chmod 644 /var/cache/apt/archives/dvpn-node-manager_latest.deb && sudo chown _apt:root /var/cache/apt/archives/dvpn-node-manager_latest.deb

Then this command to install the package: sudo apt install /var/cache/apt/archives/dvpn-node-manager_latest.deb

The CLI starts and takes me to the second screen (after Docker have been successfully installed) where it asks to "Reboot Now" or "Quit and Reboot Later".

I tried both "Reboot Now" and "Quit and Reboot Later" options and every time I try to continue with the installation the CLI screen takes me to the same request to "Reboot Now" or "Quit and Reboot Later"

Also, running the command dvpn-node-manager help returns this critical info: [INFO] Configuration files do not exist. [INFO] Please wait while the dVPN node container is being started... [ERROR] Invalid Node Type

(screenshot attached)

Checking under Docker folder, there is no configuration file created by Sentinel dVPN Node.

I tried to sudo apt autoremove the package and re-installed it again. Same results.

Is there a specific port that I need to whitelist on the firewall for the script to run?

Thank you very much.

[Loggsie]

I encountered the same issue when running under root and leaving out sudo.

Ensure to run after rebooting

sudo dvpn-node-manager

The usual configuration screen is displayed, though I did have to reboot twice to see this.

[theVasilis]

Thank you @Loggsie

Following your recommendation.

Ensure to run after rebooting

sudo dvpn-node-manager

First I get this CLI screen.

And then I'm taken here.

I still believe that during the installation the script was not able to pull any libraries or other necessary resources due to my firewall blocking all undeclared ports.

Looking forward to your advice.

[FoxinouFR]

Hi there! While waiting for me to find a debian 12 to test, I just made a change to allow the script to run with debian. Can you download (or copy-paste) the script dvpn-node-manager.sh #f5a86cb on your server and run it manually?

cd ~
wget -O dvpn-node-manager.f5a86cb.sh https://raw.githubusercontent.com/sentinelgrowthdao/dvpn-node-manager/f5a86cbab65e98dd2d706e44e3f31a3b69a793f8/dvpn-node-manager.sh
sudo bash dvpn-node-manager.f5a86cb.sh

This will solve the "Unsupported OS" problem.

[theVasilis]

Thank you very much @Loggsie

"Unsupported OS" problem has indeed been solved and here is the next error:

Looking forward to your thoughts.

[Loggsie]

Did you sudo apt remove dvpn-node-manager prior to deploying the updated script?

The error looks like a Docker container conflict.

[theVasilis]

Ok now I have a different error.

I did sudo apt remove dvpn-node-manager and then sudo apt autoremove to make sure the dependencies are reset.

Then run the latest file installation and indeed the script downloaded a lot of libraries and files.

After that the CLI screen asked me to "Reboot" or "Continue Without Rebooting". I rebooted the system and running the same file again leads me to here:

However, now I have a different warning message where it says that the Sentinel Docker image was NOT downloaded.

Finally, I can't run the command sudo dvpn-node-manager.

The system returns dvpn-node-manager: command not found

Thank you very much for your help.

[FoxinouFR]

Hi! Here's a new version running on debian 12 as root. Everything works on my side but I tested on a fresh installation of debian.

cd ~
wget -O dvpn-node-manager.277e42e.sh https://raw.githubusercontent.com/sentinelgrowthdao/dvpn-node-manager/277e42ebae767701f18f7394a341b501f2f3dca9/dvpn-node-manager.sh
sudo bash dvpn-node-manager.277e42e.sh

Please let me know if it works for you. A new version of the .deb package will be generated in the next few hours to enable command-line installation.

[theVasilis]

Thank you @FoxinouFR

That worked, I reached to a point where it asks me to send $10 DVPN to a specific wallet address or click quit and run the installer again.

Obviously I didn't know that, and I wasn't prepared. So I clicked quit, until I send the funds to the specified wallet address.

Couple of questions:

1) DVPN token on Osmosis chain or another one? I see 5 different versions on Binance Web3 Wallet 2) After i send the tokens, should I re-run the installation script? 3) Is the package going to update automatically following the .deb repository publication?

Thank you very much.

[FoxinouFR]

Thank you @theVasilis.

1. These are native $DVPN tokens from the Sentinel blockchain. You can buy them on Osmosis and then transfer them to the Sentinel blockchain. As for the Binance Wallet, I’m not sure, so I recommend asking in the Sentinel Node Network Telegram group for more information.

2. Yes, once the tokens are available at the node’s address, you can restart the script, which will lead you to the script that allows you to manage your node.

3. The .deb package will update automatically only if you have added the PPA and installed the package using the apt command. If you downloaded the .deb manually, you will need to download the new .deb versions yourself to update manually.

Thank you very much and see you soon.

[theVasilis]

@FoxinouFR thank you very much.

3. the repository doesn't have a Release file and ends with 404. See screenshot

Maybe there is some change that needs to be done to the PPA to support Debian 12?

[FoxinouFR]

hello @theVasilis ! A new release is available and the README has been updated to show how to install dvpn-node-manager with the ppa.

It may be a few hours before the alpha13 package is available on ubuntu servers. We're at your disposal if you have any other problems!

[theVasilis]

@FoxinouFR

I copied the PPA installation codes per your example from the README file and that lead to multiple keyring errors (see screenshot)

I believe that there is an error with the signing pub key for the deb PPA.

Please advice.

Thank you very much.

[FoxinouFR]

Hi theVasilis! There seems to be a problem when importing the package verification key.

Can you run the command apt-key list and search the list to see if the key `` is present. In my case I have this :

/etc/apt/trusted.gpg.d/foxinou_dvpn-node-manager.gpg
----------------------------------------------------
pub rsa4096 2024-04-19 [SC]
      1E4D CBDC 436F 9546 8F1F EB79 3B60 4A1F 5EE3 D8E5
uid [ unknown] Launchpad PPA for Foxinou

If nothing appears, run the following command again:

curl -fsSL https://files.foxinodes.net/launchpad/foxinou_dvpn-node-manager.gpg | sudo apt-key add -

You should then have the key listed in the apt-key list.

With a freshly installed debian 12, everything works fine if you follow the README.

[theVasilis]

@FoxinouFR thank you very much.

There is an error on your code to import the gpg key.

The new code structure required by Debian distros (Ubuntu, etc) has to be written like this: curl -sS https://files.foxinodes.net/launchpad/foxinou_dvpn-node-manager.gpg | gpg --dearmor | sudo tee /etc/apt/trusted.gpg.d/sentinel.gpg

Here's the relevant resource: https://itsfoss.com/apt-key-deprecated/

I followed the resource above and the gpg key was imported successfully and now the repository updates are running normally without errors.

Also, you might want to update the README file to a more organized solution like this: echo "deb http://ppa.launchpad.net/foxinou/dvpn-node-manager/ubuntu jammy main" | sudo tee -a /etc/apt/sources.list.d/sentinel.list

Instead of adding the repository sentinel.list on the main folder, I'm adding it inside the folder with the rest of added repositories.

Thank you very much for your help again.