Monero remote nodes: how to connect safely

Quick steps

1. Decide who you trust. Prefer your own node, then a trusted friend's node, then a reputable public node with SSL.
2. Get the node address. Note the host name and port, usually 18089 for public restricted nodes or an onion address for Tor.
3. Open the wallet's node settings. In Cake open Settings, Monero Settings, Nodes, in Feather open Settings, Network, in Monerujo tap the node name, in the GUI open Settings, Node.
4. Add and select the node. Enter host and port, enable SSL if offered, and select the new node.
5. Check the sync. Wait until the wallet shows it is synchronized and compare the block height with another source.

What a remote node is

A Monero node (the program monerod) stores the blockchain and relays transactions. Running one means downloading and verifying the whole chain. Mobile and light desktop wallets skip this by connecting to someone else's node, a remote node.

With a normal remote node, the wallet downloads blocks and does the scanning itself, so your private keys never leave the device. That is different from a light-wallet server, which receives your private view key and scans for you. MyMonero worked that way. Our web wallet guide explains the difference.

What the node operator can and cannot see

The Monero project's own glossary says using public remote nodes can be risky and recommends running your own node where possible. For most people a reputable remote node is still a reasonable trade-off, as long as they understand the IP exposure.

Ports: 18081, 18089 and 18080

• 18080: peer-to-peer port that nodes use to talk to each other. Wallets do not connect here.
• 18081: the default RPC port for wallets. On your own computer it is usually unrestricted and should stay private.
• 18089: the conventional port for a public, restricted RPC that only answers safe, view-only requests. Most public nodes listen here, often with SSL.
• Many public nodes also run on 443 behind HTTPS, or as Tor .onion addresses.

A node address looks like node.example.org:18089. If a node only offers 18081 publicly, be cautious: it may be misconfigured.

How to choose a node

1. Your own node is best. It can be at home and reached from your phone over Tor. See how to run a Monero node.
2. A friend's or community member's node that you trust.
3. The wallet's default node list. Cake, Feather and Monerujo ship curated lists. Convenient, but you trust the wallet developer's choice.
4. Public node lists show uptime, height and whether a node supports SSL or CORS. Some lists flag suspected spy nodes. Avoid any node that appears there.

Good signs: the node is synced (its height matches others), responds quickly, supports SSL and is run by someone with a public reputation.

How to connect in popular wallets

Cake Wallet

Open Settings (top right), tap Monero Settings, then Nodes. Tap + to add the host and port, with SSL or a SOCKS proxy if needed. Tap the node to select it and wait for Synchronized.

Feather

Click the connection icon at the bottom right or open Settings, Network, Node. Feather can route traffic through its bundled Tor. You can paste a custom node or choose from its list.

Monerujo

Tap the node name on the main screen to open the node list, then add your own node or use the built-in scan.

Monero GUI

In Settings, Node, select Remote node and enter the address and port. Simple mode connects to a remote node automatically. Advanced mode lets you pick one or run a local node, and offers a bootstrap node while your own node syncs.

Monero CLI

Start the wallet with monero-wallet-cli --daemon-address node.example.org:18089. To route through Tor, add a SOCKS proxy such as --proxy 127.0.0.1:9050 and use an onion address.

Privacy tips

• Use Tor or an onion node to hide your IP from the node operator. Feather bundles Tor, and Monero 0.18.5.0 (11 May 2026) added SOCKS5 support.
• Switch nodes if one goes offline or returns odd data. Do not keep trying a node that refuses connections.
• Avoid nodes that ask you to install anything, log in or enter keys. A real node never needs your seed.
• Remote nodes do not change how private the transaction is on-chain. They only affect network-level privacy.

Troubleshooting a node connection

• Stuck on connecting: the node may be offline or overloaded. Try another one before changing anything else.
• Sync stops at an old height: the node itself may be behind. Compare its height with network stats and switch if it lags.
• SSL errors: some nodes use self-signed certificates. Turn SSL off only for nodes you run yourself on a trusted network.
• Very slow first sync: a restore from an early height has to download many blocks. Set a realistic restore height; see restoring a wallet.
• Balance looks wrong after switching nodes: rescan the wallet. A good node and a correct restore height fix almost every case.

Rate your setup with our privacy checklist.

Frequently asked questions