−25%

on annual Windows plans, until 31 Oct. See plans

EQVPS
Get started

Run your own Monero node on a VPS (full node, not mining)

Sep 2, 2026 · 3 min read · EQVPS Team

If you use Monero seriously, the weakest link is often the remote node your wallet connects to. A public node's operator can see which outputs your wallet asks about and the IP it comes from — not the amounts, but more metadata than you might want. Running your own full node on a VPS removes that middleman: your wallet talks only to a daemon you control, and as a bonus you add a relay to the network.

To be clear about scope: this is a full node (monerod), not mining. It validates and relays the chain and serves your wallet — it does not solve proof-of-work for rewards. (Mining is CPU-heavy and not allowed on our shared NAT plans; a node is fine.)

What a Monero node needs

  • A dedicated IPv4. A good node accepts inbound P2P on port 18080 so it helps relay — that needs a dedicated-IP plan. Our NAT plans can't take inbound, so take Micro-IP or Small-IP (from $10/mo).
  • Enough disk. The Monero blockchain is large and grows steadily. Pick a plan with disk headroom, or run a pruned node (roughly a third of the size) if space is tight.
  • Modest RAM/CPU. 2 GB RAM is comfortable for monerod. NVMe helps the initial sync a lot.
  • An EU location. Germany or Finland — clean routes, real data-protection law.

Set up monerod (Ubuntu 24.04)

# dedicated-IP plan, run the daemon as a non-root user
adduser --disabled-password --gecos "" monero
su - monero

# download the official binaries (verify the hash from getmonero.org)
curl -L -o monero.tar.bz2 https://downloads.getmonero.org/cli/linux64
tar xjf monero.tar.bz2 && cd monero-x86_64-*/

cat > monerod.conf <<'EOF'
data-dir=/home/monero/.bitmonero
p2p-bind-ip=0.0.0.0
p2p-bind-port=18080          # inbound P2P — open this in the firewall
rpc-bind-ip=127.0.0.1        # keep RPC on localhost (do NOT expose to the internet)
rpc-bind-port=18081
prune-blockchain=1           # optional: pruned node, ~1/3 the disk
no-igd=1
out-peers=32
in-peers=64
EOF

./monerod --config-file monerod.conf --detach
./monerod status              # watch it sync

Open only the P2P port; keep RPC private:

# as root
ufw allow 18080/tcp           # P2P relay
# do NOT open 18081 to the world — wallet-RPC stays on localhost / your IPs only

Point your wallet at it

In the official GUI/CLI wallet, set the daemon address to your VPS on 18081 only over a private channel (SSH tunnel, WireGuard/VLESS, or restrict 18081 by firewall to your own IPs). Your wallet now validates against a node you trust, with no third-party remote node in the middle.

Why EQVPS for a Monero node

  • Dedicated IPv4 from $10/mo, all ports you choose, self-service reverse DNS.
  • EU locations (Germany, Finland) — clean routes, real data-protection law.
  • No KYC, crypto payment. Email to sign up, USDC/USDT to pay — fitting for a privacy-coin node.
  • Root in ~60 seconds, NVMe. Fast initial sync; run pruned if you want a smaller footprint.

Honest scope: a full node improves your wallet's privacy and helps the network — it is not anonymity by itself, and it is not mining. Keep RPC off the public internet.

Anonymous VPS hosting explained → · Run a Bitcoin node on a VPS → · Pay for your VPS with Monero →

FAQ

Is this mining?

No — this is a full node, not mining. A Monero node (monerod) validates and relays the blockchain and answers your wallet; it does not solve proof-of-work for block rewards. Mining is a different, CPU-heavy activity and is not permitted on our shared NAT plans; a full node is fine and is what this guide covers.

Why run my own node instead of a public remote node?

When your wallet uses someone else's remote node, that operator sees which transactions you request and your IP. Your own node removes that middleman: your wallet talks only to a daemon you control. You also stop trusting a stranger's node to be honest and online, and you add a relay to the network.

Which plan does a Monero node need?

A dedicated-IPv4 plan so the node can accept inbound P2P on port 18080. 2 GB RAM is comfortable; the blockchain is large and growing, so pick disk accordingly (an SSD-backed plan with room to spare, or prune it). Micro-IP/Small-IP work well; a Pro plan if you want lots of headroom.

Do I need to open ports?

For a well-behaved node, allow inbound TCP 18080 (P2P) so you help relay. Keep the RPC port (18081) bound to localhost or firewalled to your own IPs — never expose an open wallet-RPC to the internet. The setup below does this.

Do you ask for ID or a card?

No. Register with an email, pay in USDC or USDT. No documents, no card, no KYC.

Comments

No comments yet. Be the first.

Leave a comment

Comments are moderated before they appear.