Documentation

Inery Node Setup & Startup Guide

Complete guide for Genesis, Master, and Lite node deployment with monitoring and GUI.

This guide covers local and remote deployments, integrated monitoring, and GUI components for node management and visualization.

1. Prerequisites

System Requirements

  • Operating System: Ubuntu 22.04 or later (Ubuntu 24.04 recommended for WSL / package installs)
  • Inery Software Pack: Latest version (included in the repository)
  • Network Access: SSH access and Git installed on the machine

Required Setup Steps

  1. Ensure SSH terminal access and Git are installed on your Ubuntu machine.
  2. Clone the Inery Node repository:
git clone https://oauth2:[email protected]/inery-groupy/inery-node.git
  1. Navigate to the project directory:
cd inery-node

Note: For local instance deployment, a genesis node is required. You may optionally add master or lite nodes.

2. Running a Local Genesis Node (Linux)

Step 1 — Configure Node Settings

Edit config.ini.example (or your active config) with:

  • Node Type: Genesis, Master, or Lite
  • URL Configuration: Set appropriate network URLs
  • Port Settings: Define custom ports if required
  • Authorization: Configure authentication credentials

By default, parameters are pre-configured for Genesis and Master node types. For local deployment, ensure you have a genesis instance configured.

Step 2 — Start Inery Node Protocol

From the inery-node directory:

./start.py

This initializes the Inery Node protocol and starts the node.

Step 3 — Verify Node Activity

Method A — CLI

cline get info

If you changed the client port, pass a custom URL:

cline -u http://127.0.0.1:8888 get info

Method B — Node logs

tail -f nodes/inery/nodine.log

nodine.log contains all process logs for the running node. When healthy, you should see newly created or received blocks logged continuously.

Method C — Monitoring Dashboard

Open:

http://localhost:7778

The monitoring interface tracks the nodine protocol by reading the nodine log file and provides historical query and audit log inspection.

3. Genesis Node Initialization

Activate system contracts and memory by running:

./genesis_setup.py

Wallet Setup

To sign transactions, a wallet is required. If you do not have an existing wallet, one is created automatically during genesis setup and stored for future signing.

Transaction Monitoring

After genesis setup:

  1. Open the New Transactions area in the monitoring dashboard
  2. Observe logged transactions as they are processed
  3. Follow each transaction back to the block that recorded it
  4. Inspect signatures, cryptographic details, and action data structures

Each transaction consists of one or more actions. Actions are defined by contract logic compiled to WebAssembly (WASM) and executed on the Inery NodeVM (internal to the nodine process).

4. GUI Launch & Navigation

Setup

./setup_gui.py

This command:

  • Activates the Inery GUI service
  • Configures the .env file with database credentials
  • Generates private keys for the GUI database

Then open:

http://localhost:8080

Create a Database Composition

  1. Register a new database
  2. Create a new composition (schema)
  3. Configure tables and fields

5. Migration Plugins and Data Import

Inery provides multiple ways to import structures and records into IneryDB.

Multi-format Import

  • CSV
  • JSON
  • XML

Database Instance Import

  • Redis
  • MongoDB
  • Other supported databases

AI Architect

Describe your database structure in English; AI Architect generates an IneryDB schema automatically.

SQL Database Migration

  1. Export your SQL database as a .sql dump
  2. Provide the dump to the Inery migration service
  3. Models analyze the SQL structure and create an optimal NoSQL schema
  4. Migrate data to IneryDB with preserved relationships

Important: Back up data before migration. Test in a development environment first.

6. Setting Up Inery Node on Windows

Inery Node is built for Linux (Ubuntu). On Windows, use one of these paths:

  1. Option A: Docker Desktop (recommended) — isolated container via Dockerfile / docker-compose.yml
  2. Option B: WSL 2 — native Ubuntu 24.04 shell on Windows

Option A — Docker Desktop (Recommended)

Prerequisites

  1. Install Docker Desktop for Windows
  2. Enable Use the WSL 2 based engine (default)
  3. Start Docker Desktop and wait until it is fully running

Setup & Run

cd path\to\inery-node
docker-compose up -d --build
docker-compose ps

Mapped ports

| Service | URL / Port | | :--- | :--- | | Monitoring Dashboard | http://localhost:7778 | | Inery Node RPC API | http://localhost:8888 | | Database GUI Panel | http://localhost:8080 | | P2P Network | 9010 | | Wallet (kined) | 8900 |

Useful Docker commands

docker-compose logs -f
docker-compose stop
docker-compose start
docker-compose down -v && docker-compose up -d

Post-start setup (Genesis + GUI)

Wait ~15–30 seconds after docker-compose up -d, then confirm the node is live:

docker exec inery-node-container curl -s http://localhost:8888/v1/chain/get_info

You should receive JSON with head_block_num.

One-click full setup (recommended)

docker exec -it inery-node-container python3 /app/setup_all.py

This waits for node health, runs full Genesis bootstrap, and launches the GUI. When finished you should see endpoints for:

  • Monitoring: http://localhost:7778
  • GUI: http://localhost:8080
  • RPC: http://localhost:8888

Manual setup

  1. Bootstrap Genesis:
docker exec -it inery-node-container python3 /app/scripts/genesis_setup.py

Phases: protocol pre-activation → system accounts → system/boot contracts → initial INR/BYTE supply → GUI contract & plugins. Safe to re-run.

  1. Configure & start GUI:
docker exec -it inery-node-container python3 /app/scripts/setup_gui.py --force

Optional flags: --port, --domain, --https, --proxy, --force.

  1. Verify:
docker exec inery-node-container curl -s http://localhost:8888/v1/chain/get_info
docker exec inery-node-container curl -s -o /dev/null -w "%{http_code}" http://localhost:8080
docker exec inery-node-container curl -s -o /dev/null -w "%{http_code}" http://localhost:7778

Restart GUI only:

docker exec inery-node-container pkill -f inery-gui
docker exec -it inery-node-container python3 /app/scripts/setup_gui.py --force

Option B — WSL 2 (Native Ubuntu)

  1. Install Ubuntu 24.04 LTS (PowerShell as Administrator):
wsl --install -d Ubuntu-24.04
  1. Open the Ubuntu terminal and go to your repo (Windows drives are under /mnt/):
cd /mnt/c/Users/YourUsername/path/to/inery-node
  1. Install dependencies:
sudo apt-get update && sudo apt-get install -y \
  python3 python3-pip python3-venv python3-dev \
  curl libpq5 procps lsof git build-essential sudo
  1. Install monitoring Python packages:
pip3 install -r inery-monitoring/requirements.txt --break-system-packages
  1. Install Inery Core package:
sudo dpkg -i packages/inery-core/inery.2.1.0-3-ubuntu-24.04_amd64.deb \
  || sudo apt-get install -f -y
  1. Configure config.ini, then start:
python3 start.py
python3 genesis_setup.py

7. Troubleshooting

Common Issues

  • Node not starting: Verify prerequisites and port availability
  • Port conflicts: Ensure ports 8888, 7778, 8080, 9010, and 8900 are free
  • Git clone fails: Verify network connectivity and authentication credentials
  • GUI not accessible: Confirm GUI setup completed and the service is running

Always review nodes/inery/nodine.log (or docker-compose logs) for errors.

Data Persistence

  • Docker: Blockchain data lives in Docker volumes inery-data and inery-wallet (kept across stop/rebuild)
  • WSL 2: State is stored under your local nodes directory

Windows: Port Mapped but Not Reachable

Symptom: docker-compose ps shows the container Up and ports mapped, but http://localhost:8888 refuses connection.

Cause: Usually Windows CRLF (\r\n) line endings corrupted scripts after cloning on Windows, so the node process never starts inside the container.

Fix

docker-compose down -v
docker-compose build --no-cache
docker-compose up -d
docker-compose logs --tail=60

Look for active block production. To check CRLF inside the container:

docker exec -it inery-node-container bash -c "cat -A /entrypoint.sh | head -5"

If you see ^M at line ends, rebuild with --no-cache. Prevent future conversion:

git config --global core.autocrlf false
git clone https://oauth2:[email protected]/inery-groupy/inery-node.git

The repository includes .gitattributes to enforce LF line endings.

Inery Node Setup & Startup Guide | Version 1.0

Previous Page<-IntroductionNext PageInery Wallet Guide->