To run a headless Ravencoin full node on Ubuntu, install the official Ravencoin Core Linux binaries, configure ravend under a dedicated unprivileged account, and supervise it with systemd. The node validates and relays Ravencoin data; it does not mine RVN or require a wallet. This guide covers mainnet, safe RPC defaults, synchronization checks, inbound peer access, and routine maintenance.
What a Ravencoin node does
ravend is the Ravencoin Core daemon; raven-cli sends commands to it over the node’s RPC interface. The optional raven-qt program provides a graphical interface and is not needed on Ubuntu Server. Ravencoin Core downloads transaction history and participates in validating and relaying network data. The project documentation describes the Core client and its role.
A full node is not a miner, mining pool, block explorer, or wallet service. It does not produce RVN income. You do not need RVN or a wallet just to synchronize and operate a node.
Before you install
- Use a supported 64-bit Ubuntu installation and a terminal or SSH access. The standard Linux release asset is for x86-64; check the asset architecture before downloading.
- Use an SSD with room for the blockchain, logs, and future growth. Current storage needs change with chain growth; check available disk space rather than relying on a fixed figure.
- Plan for adequate RAM and a stable connection without restrictive data caps. At least 2 GB RAM is a practical starting point, with more preferable for a VPS or a machine running other services.
- A public IPv4 address or working IPv6 and router or provider firewall access are needed only if you want other peers to initiate connections. A node can synchronize using outbound connections without inbound access.
- The default setup below is for mainnet. Keep testnet in separate configuration and data directories; older testnet guidance in the project wiki is development material, not a production-node recipe.
A home server avoids a recurring hosting bill but may have upload limits, dynamic addressing, power interruptions, or carrier-grade NAT. A VPS generally offers a public IP and simpler uptime management, but check persistent disk, bandwidth, regional availability, and provider terms. Hosting is optional.
Recommended Free Tools
#1 Best Overall
- Includes Raspberry Pi 5 with 2.4Ghz 64-bit quad-core CPU (8GB RAM)
- Includes 128GB Micro SD Card pre-loaded with 64-bit Raspberry Pi OS, USB MicroSD Card Reader
- CanaKit Turbine Black Case for the Raspberry Pi 5
- CanaKit Low Noise Bearing System Fan
- Mega Heat Sink - Black Anodized
Install the command-line tools
For most users, the prebuilt official release is simpler than compiling. It avoids setting up a compiler and build dependencies; source builds are better suited to developers, patch testing, or unsupported platforms. The project’s build notes are developer-oriented. Review the documentation if you choose to build from source.
- Update Ubuntu and install archive and verification utilities:
sudo apt update sudo apt install -y ca-certificates curl wget tar unzip gnupg openssl - Open the official Ravencoin Core releases page. Select the stable release marked “Latest,” confirm the Linux x86-64 asset and copy its exact filename and URL. Release metadata can be inconsistent, so do not assume a version or asset name based on an older guide.
- Download the selected asset to a temporary directory. Replace the quoted value with the exact asset URL shown on the release page:
cd /tmp curl -LO 'OFFICIAL_RELEASE_ASSET_URL' - Verify the download before installing it. Compare its SHA-256 output with the checksum published for that exact asset on the official release page:
sha256sum raven-<VERSION>-x86_64-linux-gnu.tar.gzIf the release supplies a signed checksum file, verify the signature using the current signing key and fingerprint published by the project, then check the listed hashes:
gpg --import RELEASE_SIGNING_KEY.asc gpg --verify SHA256SUMS.asc sha256sum --check SHA256SUMSDo not rely on a fingerprint copied from an old guide. The release page instructs users to verify file hashes: check its current verification details.
- Extract the archive in accordance with its format. For a tar archive:
tar -xzf raven-<VERSION>-x86_64-linux-gnu.tar.gzFor a ZIP archive, use
unzipinstead. Install the binaries from the extracted release directory, adjusting the directory name to match the archive:Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchSpecial offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.sudo install -o root -g root -m 0755 raven-<VERSION>/bin/ravend /usr/local/bin/ravend sudo install -o root -g root -m 0755 raven-<VERSION>/bin/raven-cli /usr/local/bin/raven-cli - Confirm that the executables run:
ravend --version raven-cli --version
Use only the official release page rather than third-party binary mirrors. The project documentation includes old Ubuntu dependency lists; prefer the prebuilt binary and install an additional library only if an actual loader error identifies it.
Create a dedicated service account
Do not run a long-lived network daemon as root. Create an unprivileged system account and a private data directory:
sudo adduser --system --group --home /opt/ravencoin raven
sudo install -d -o raven -g raven -m 0750 /opt/ravencoin
sudo install -d -o raven -g raven -m 0700 /home/raven/.ravenCheck the account’s actual home directory before relying on the paths above:
getent passwd ravenThe usual data directory is .raven in the running user’s home. If the account’s home is not /home/raven, change every configuration, service, and CLI path below to match the path reported by getent.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #2
- Includes Raspberry Pi 5 16GB with 2.4Ghz 64-bit quad-core CPU (16GB RAM)
- Includes 128GB Micro SD Card pre-loaded with 64-bit Raspberry Pi OS, USB MicroSD Card Reader
- CanaKit Turbine Black Case for the Raspberry Pi 5
- CanaKit Low Noise Bearing System Fan
- Mega Heat Sink - Black Anodized
Configure mainnet and keep RPC private
Create the configuration file as the service user:
sudo -u raven install -d -m 0700 /home/raven/.raven
sudo -u raven nano /home/raven/.raven/raven.confUse this conservative starting configuration:
server=1
daemon=0
# RPC is local-only by default.
rpcbind=127.0.0.1
rpcallowip=127.0.0.1
rpcuser=CHANGE_THIS_USER
rpcpassword=CHANGE_THIS_LONG_RANDOM_PASSWORD
# Mainnet peer-to-peer port.
port=8767
listen=1
maxconnections=40Generate a unique password locally with openssl rand -base64 32, and replace both sample credential values. Confirm the selected release supports the authentication options you use; run raven-cli help and consult the release’s documentation if needed. Older community examples use rpcuser and rpcpassword, but do not assume every release supports only that method. The community pool example is not a security standard.
daemon=0 keeps the process in the foreground for systemd to supervise. Do not expose RPC to the public Internet. The project documents mainnet port 8767 for peer-to-peer traffic and 8766 for RPC; see its port reference.
Restrict the configuration file because it contains RPC credentials:
sudo chown raven:raven /home/raven/.raven/raven.conf
sudo chmod 600 /home/raven/.raven/raven.confStart the daemon once and confirm it responds
Test the daemon in the foreground before setting up automatic startup:
sudo -u raven /usr/local/bin/ravend
-datadir=/home/raven/.raven
-conf=/home/raven/.raven/raven.confIn a second terminal, query the node using the same data directory and configuration:
raven-cli
-datadir=/home/raven/.raven
-conf=/home/raven/.raven/raven.conf
getblockchaininfoOn first launch, the daemon creates its data files and begins finding peers and synchronizing. In getblockchaininfo, initialblockdownload is normally true during initial sync; blocks should move toward headers, while verificationprogress approaches completion. Connections can be zero briefly while the node is starting or finding peers.
Stop the foreground test cleanly with Ctrl+C before moving to systemd. To inspect available commands in the installed version, run raven-cli help.
Run it continuously with systemd
Create /etc/systemd/system/ravend.service:
sudo nano /etc/systemd/system/ravend.serviceUse this unit, which runs the daemon in the foreground and lets systemd restart it after a failure:
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Rank #3
- CanaKit Raspberry Pi 5 Essentials Starter Kit
[Unit]
Description=Ravencoin Core daemon
After=network-online.target
Wants=network-online.target
[Service]
Type=simple
User=raven
Group=raven
ExecStart=/usr/local/bin/ravend -datadir=/home/raven/.raven -conf=/home/raven/.raven/raven.conf -printtoconsole
ExecStop=/usr/local/bin/raven-cli -datadir=/home/raven/.raven -conf=/home/raven/.raven/raven.conf stop
Restart=on-failure
RestartSec=10
TimeoutStopSec=120
PrivateTmp=true
NoNewPrivileges=true
ProtectSystem=full
ProtectHome=read-only
ReadWritePaths=/home/raven/.raven
[Install]
WantedBy=multi-user.targetCheck that the selected binary recognizes -printtoconsole before using it. If it does not, remove that argument and inspect the daemon’s normal log file instead. The service’s read-only home protection is paired with an explicit writable data directory.
Load the unit, enable startup at boot, and start the service:
sudo systemctl daemon-reload
sudo systemctl enable --now ravendInspect service state and follow its logs:
systemctl status ravend --no-pager
journalctl -u ravend -fStop or restart the service cleanly with sudo systemctl stop ravend or sudo systemctl restart ravend. Avoid kill -9 except as a last resort; abrupt termination can make recovery harder.
Allow inbound peers without exposing RPC
For a host using UFW, first preserve SSH access before enabling the firewall. Then allow inbound Ravencoin peer traffic only if you want the node to accept incoming peers:
sudo ufw allow OpenSSH
sudo ufw enable
sudo ufw allow 8767/tcp
sudo ufw status verboseDo not open TCP 8766 to the Internet. If remote RPC administration is essential, use a VPN, SSH tunnel, or tightly restricted private network and source addresses; never use rpcallowip=0.0.0.0/0 on an Internet-facing host.
For inbound reachability, all of these must be true: listen=1 is enabled, the Ubuntu firewall permits TCP 8767, any cloud security group permits it, and a home router forwards it to the Ubuntu host if applicable. Carrier-grade NAT or provider policy can prevent inbound connections even when the local firewall is open.
Check synchronization, connections, and reachability separately
Run these commands as the account that has access to the configuration, or use the service account explicitly:
| Goal | Command | What it tells you |
|---|---|---|
| Blockchain status | sudo -u raven raven-cli -datadir=/home/raven/.raven getblockchaininfo |
Block progress, headers, initial download state, and verification progress. |
| Network status | sudo -u raven raven-cli -datadir=/home/raven/.raven getnetworkinfo |
Network and connection information exposed by the installed release. |
| Peer details | sudo -u raven raven-cli -datadir=/home/raven/.raven getpeerinfo |
Information about individual connected peers. |
| Connection count | sudo -u raven raven-cli -datadir=/home/raven/.raven getconnectioncount |
The current number of peer connections. |
| Supported RPC commands | sudo -u raven raven-cli -datadir=/home/raven/.raven help |
Commands available in this installed version. |
A nonzero connection count does not prove inbound reachability: outbound peers alone can keep a node connected and synchronized. Check local sockets separately:
Rank #4
- All-in-One Complete Kit: This SANOOV RPi 5 bundle comes with Raspberry Pi 5 4GB RAM single board, active cooler, durable ABS case and screwdriver. No extra parts needed, ready to use right out of the box for beginners and hobbyists
- Powerful Single Board Computer: Equipped with 4GB RAM and high-performance processor, delivers fast running speed for 4K playback, AI projects, programming and daily computing tasks. SANOOV for raspberry pi 5 4GB is equipped with broadcom 64 quad-core Arm Cortex A76 processor with gigabit ethernet and upgraded with IEEE 802.11ac Wi-Fi, Bluetooth 5.0 dual-band 2.4Ghz and 5Ghz and Power Over Ethernet (POE). Upgrading delivers 2-3 x speed vs Pi 4, redefining the experience
- Efficient Active Cooler: Effectively lowers operating temperature and prevents performance throttling. Runs quietly even under long-time heavy load, ensures stable operation all day long. SANOOV RPi 5 4GB kit offer an active cooler, which combines an aluminium heatsink with a high-performance PWM fan. Active cooler is fully compatible with the Pi OS, which can effectively reduce the temperature of RPi5 and ensure its good performance during long-term high load operation
- Sturdy ABS Protective Case: Well-fitted for Raspberry Pi 5 board, can be secured with 4 screws to effectively protect the Pi 5 motherboard from damage, reserves full access to all ports and buttons. SANOOV uses ABS material to produce the case, which has a softer texture and feel. Meanwhile, SANOOV case adopts a layered design for easy disassembly and installation. (Tip: The Case cannot install M.2 HAT Add on Board and Solid State Drive!)
- Wide Application & Full Compatibility: Seamlessly compatible with official OS and mainstream peripheral accessories for Raspberry Pi 5. Whether you are a beginner, student, electronics hobbyist or professional developer, this all-in-one kit meets your diverse needs. It excels in IoT projects, robotics design, retro gaming devices, home media servers and other DIY creations. Backed by a large global community, you can easily find guides, technical support and shared projects online
sudo ss -lntp | grep -E '8766|8767'RPC should listen on a loopback address such as 127.0.0.1:8766. P2P may listen on 0.0.0.0:8767, [::]:8767, or a specific interface, depending on configuration. A local listener and firewall rule still do not prove external reachability; router forwarding, cloud firewall rules, public addressing, and ISP networking also matter.
Troubleshoot common failures
ravend: command not found
Check the installation path, executable format, and machine architecture:
command -v ravend
file /usr/local/bin/ravend
uname -mReinstall from the correct official archive if the binary is missing or incompatible.
Permission denied
Inspect ownership and permissions:
ls -l /usr/local/bin/ravend
ls -ld /home/raven/.raven
ls -l /home/raven/.raven/raven.confIf needed, restore service-user ownership and restrictive access:
sudo chown -R raven:raven /home/raven/.raven
sudo chmod 700 /home/raven/.raven
sudo chmod 600 /home/raven/.raven/raven.confThe service exits or restarts repeatedly
Read recent logs, then run the daemon in the foreground to see startup errors directly:
journalctl -u ravend -n 100 --no-pager
sudo -u raven ravend -datadir=/home/raven/.raven -conf=/home/raven/.raven/raven.conf -printtoconsoleCommon causes include invalid configuration, a port already in use, data-directory permissions, incomplete or damaged chain data, an incompatible architecture, a missing shared library, or a daemonization flag that conflicts with systemd. Check for missing libraries with:
ldd /usr/local/bin/ravend | grep 'not found'RPC connection refused
Confirm the daemon is running and RPC is listening locally:
sudo systemctl status ravend --no-pager
sudo ss -lntp | grep 8766Make sure raven-cli uses the same data directory and configuration as ravend. An incorrect path, credentials, bind address, or service-user home can make the CLI appear unable to reach a running node.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Best Value
- 【What you Get】You will get 1*Pi 5 8GB Single Board,1*RasTech Case,1*Active Cooler,1*Screwdriver,1*Installation instructions,12-month free warranty, lifetime service, 24-hour prompt and friendly response.
- 【More Connectors】There are two USB 3.0 ports(5Gbps simultaneously) and two USB 2.0 ports, which triple total bandwidth ,support any combination of up to two cameras or displays. Peak SD card performance is doubled through support for the SDR104 high-speed mode. It provides a smooth desktop experience for you. Offer Gigabit Ethernet and a PCIe interface, along with dual-band Wi-Fi and Bluetooth 5.0/BLE wireless capability. The RasTech Pi 5 Kit use the new 27W 5.1V 5A USB-C power connector.
- 【 Support Dual 4Kp60 Display 】Each of the two microHDMI sockets can control a 4K display at 60 Hertz, now support HDR, offering super HD video for media streaming projects. RPi 5 is the first RPi model that comes with a PCI Express port (PCIe 2.0 x1 with 500 MB/s) to attach SSDs (requires separate M.2 HAT).
- 【 Excellent Chips And Applications】Pi 5 is a full-size Pi computer using silicon built in-house at Pi. The RP1 “southbridge” provides the bulk of the I/O capabilities for Pi 5. Pi 5 is more friendly and convenient in the development of Internet of Things, Web development, machine identification, automatic control and other electronic equipment applications and network.
- 【 Faster CPU, Better GPU 】 Pi 5 features a Broadcom BCM2712 64-bit quad-core Arm Cortex-A76 processor running at 2.4GHz, it delivers a 2–3× increase in CPU performance relative to RaspberryPi 4. The 800MHz VideoCore VII GPU is compatible to OpenGL ES 3.1 and Vulkan 1.2, substantial uplift in graphics performance. Pi 5 Offers lightning-fast CPU speed, a PCI Express interface, a Real Time Clock (RTC) and a power button and runs significantly cooler than Pi 4.
No peers or synchronization is not advancing
Check network status and recent logs, then check the host’s resources:
sudo -u raven raven-cli -datadir=/home/raven/.raven getnetworkinfo
sudo -u raven raven-cli -datadir=/home/raven/.raven getconnectioncount
journalctl -u ravend --since "30 minutes ago"
df -h
free -h
uptimeInvestigate outbound firewall or DNS restrictions, system time, a full disk, memory pressure, or a temporary peer-discovery issue. For inbound access, also check listen=1, TCP 8767 at each firewall layer, router forwarding, and IPv4 or IPv6 routing. Inbound access is not required for synchronization.
Suspected database corruption
Do not delete .raven as a first step. Stop the service, preserve raven.conf and any wallet files, inspect logs, and use recovery options documented for the installed release before considering a chain-data rebuild. Removing the directory can delete wallet data as well as blockchain data, and a full resynchronization can take substantial time and storage.
Back up and upgrade safely
Before an upgrade, stop the node cleanly and preserve its configuration and data. For example:
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minutesudo systemctl stop ravend
sudo cp -a /home/raven/.raven/raven.conf /root/raven.conf.backup
sudo cp -a /home/raven/.raven /root/raven-data-backupFor a pure node with no wallet, the configuration is still essential. If a wallet exists, preserve its wallet files and credentials securely; blockchain data and wallet data are not interchangeable, and a server-side copy is not a substitute for a protected backup. Install only a verified official release, then start the service and monitor it:
sudo systemctl start ravend
sudo journalctl -u ravend -f
ravend --version
sudo -u raven raven-cli -datadir=/home/raven/.raven getnetworkinfoOptional choices: pruning, wallet, and source builds
Pruned or archival data
An archival node retains the full chain history. A pruned node discards older block data after validation, reducing storage use but limiting applications that need historical block or transaction data. Pruning does not remove the node’s core validation role. Check the installed release’s help and documentation for supported pruning settings and consequences before enabling them; do not copy a pruning value from an unrelated pool guide.
Wallet functionality
A network-only node does not need a wallet or a generated address. Keep private keys off the server unless wallet functionality is necessary. If you do use a wallet, encrypt it and maintain a separate secure backup.
Compiling from source
Build from the official Ravencoin repository only when you need a patch, a specific branch, or a platform not covered by the release binaries. Follow the repository’s current Unix build notes rather than relying on legacy Ubuntu package lists.
Free tools Windows power users keep installed
One-click scans. No signup required.
What this setup does not provide
This configuration runs a mainnet node with local RPC administration and optional inbound peer access. It does not configure mining, a mining pool, a block explorer, or a public RPC service. Those are separate systems with additional software, security, resource, and operational requirements.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
