Monero (XMR) Blockchain v6.2.4

Release Date: October 22, 2026 Tags: MONERO, XMR, WALLET-RPC, DAEMON LOGIN, DIAGNOSTICS

Overview

A monerod with a login of its own can now be used. The platform held one RPC username and password and sent it to three places: to monero-wallet-rpc, to monerod, and to monero-wallet-rpc again as the daemon login whenever it pointed a wallet at the daemon. A monerod whose --rpc-login differed from the wallet RPC's therefore could not work. Every refresh failed with error -38, "no connection to daemon", and changing --daemon-login on the wallet RPC's command line changed nothing, because the login the platform sent when it pointed the wallet at the daemon replaced the one wallet-rpc was started with.

The daemon can now have its own pair, XMR_DAEMON_RPC_USER and XMR_DAEMON_RPC_PASSWORD. And a refresh that still cannot reach the daemon now says in the log which side is broken, instead of the bare -38 that fits three different faults.

No new requirement: Core v6.7.9 and Ecosystem v6.5.3, as before.

Update Instructions

pnpm updator

No schema change and no seeder. An install whose monerod and wallet RPC share one --rpc-login needs no .env change. The backend and the cron process restart at the end.

Upgrade Notes

Give the daemon its own login when it differs from the wallet RPC's

• If monerod and monero-wallet-rpc run with the same --rpc-login, change nothing. XMR_RPC_USER and XMR_RPC_PASSWORD serve both, exactly as before.
• If monerod's --rpc-login is different, add it to .env as XMR_DAEMON_RPC_USER and XMR_DAEMON_RPC_PASSWORD, then restart the backend and the cron process. XMR_RPC_USER and XMR_RPC_PASSWORD stay the wallet RPC's login. Set both settings or neither: one alone is ignored, with a warning in the log, because HTTP Digest needs both.
• v6.2.3 said to start monero-wallet-rpc with --daemon-login <XMR_RPC_USER>:<XMR_RPC_PASSWORD>. When the daemon has its own pair, that flag takes the daemon's login, <XMR_DAEMON_RPC_USER>:<XMR_DAEMON_RPC_PASSWORD>. It is the login the platform sends when it points a wallet at the daemon, and that login replaces the flag, so the two should match.
• The admin Requirements page belongs to the Ecosystem add-on. Before Ecosystem v6.6.1 it checks monerod with XMR_RPC_USER and XMR_RPC_PASSWORD only, so a daemon with its own login can show as refusing there while the platform uses it without trouble. Update Ecosystem to see the right answer; nothing else depends on it.

Reading the new log line

• When a refresh still fails with -38 after the platform has pointed the wallet at the daemon, the log says Wallet refresh cannot use the daemon: and which side is broken, at most once every two minutes in each process. The backend cannot log in to monerod means the daemon's login in .env is not monerod's --rpc-login. monerod answers the backend, so the fault is on wallet-rpc's side means the daemon is up and the login is right, and monero-wallet-rpc is the one that cannot reach it: it runs somewhere 127.0.0.1 is not this monerod, its --daemon-ssl does not match monerod's --rpc-ssl, or its wallet files are for another network. The backend cannot reach monerod means the daemon is down or the address is wrong. The line never contains a username or a password.

Added

The daemon's own login

• Added XMR_DAEMON_RPC_USER and XMR_DAEMON_RPC_PASSWORD. When both are set they are the login for every call the platform makes to monerod, and the daemon login it gives monero-wallet-rpc when it points a wallet at the daemon. monero-wallet-rpc itself is always addressed with XMR_RPC_USER and XMR_RPC_PASSWORD. When neither is set, the one pair serves both services, byte for byte as before.
• A login that an RPC refuses now names the keys that answer for that service. A daemon that asks for a login nobody configured says so with the daemon's keys, not the wallet's.

A refresh that cannot reach the daemon says why

• Added the explanation. After the re-point and its one retry both fail, the platform asks monerod itself, with the login it would use for it, and writes one line: the daemon refuses the login, the daemon cannot be reached, or the daemon answers and the fault is on wallet-rpc's side. It is throttled to once per two minutes in each process, because a pass over many wallets fails the same way for each, and it never throws.
• The warning the platform gives when wallet-rpc opens wallets without a working daemon connection now names the daemon's login, not always the wallet RPC's.

Fixed

The login set_daemon sent was always the wallet RPC's

• Fixed the pair sent as the daemon login when the platform points a wallet at the daemon. It was XMR_RPC_USER and XMR_RPC_PASSWORD whatever monerod required, and it replaced the --daemon-login that monero-wallet-rpc was started with. With a monerod login that differed, it undid a correct launch command each time it ran. It is now the daemon's login.
• Fixed the same for the platform's own requests to the daemon, get_info, get_height and the transaction lookups: a daemon with its own login was answered with the wallet RPC's.