Common issues — start here

Help & Support
1

Before opening a new help thread, check whether your problem is in this
list. If it is, the answer here is usually faster than waiting for a reply.

“Could not connect to server 127.0.0.1:2211”

intcoind isn’t running, or RPC isn’t bound to localhost.

pgrep intcoind            # is the daemon up?
systemctl status intcoind # if you installed via systemd
grep rpcbind ~/.intcoin/intcoin.conf

If rpcbind= is missing or set to a LAN IP, RPC won’t accept loopback.
Either add rpcbind=127.0.0.1 or pass -rpcconnect=<the bound IP> to intcoin-cli.

“Initial block download is in progress”

The node hasn’t caught up yet. RPC methods like sendtoaddress and
getblocktemplate block during IBD. Wait it out — getblockchaininfo
shows verificationprogress (0.0 to 1.0).

Stuck progress? See the Node Operation help category.

“Wallet is locked”

You encrypted the wallet but didn’t unlock it.

intcoin-cli walletpassphrase <your-passphrase> 600

600 = unlock for 10 minutes. Increase if you’re doing many ops.

Mining produces 0 H/s

Three usual causes:

  1. Mining address is invalid for the network. int1q... for mainnet,
    tint1q... for testnet, sint1q... for signet. Bech32 checksums
    differ — you can’t just swap prefixes.
  2. RPC credentials wrong. Check -rpcuser / -rpcpassword against
    the node’s intcoin.conf.
  3. Node is in IBD. getblocktemplate refuses until sync completes.

Where the logs are

Service Path
intcoind (Linux, default datadir) ~/.intcoin/debug.log
intcoind (systemd) journalctl -u intcoind --no-pager
Qt wallet Help → Debug Window → Console / About → Open Logs

Still stuck?

Open a new topic in the right sub-category:
Wallet ·
Node Operation ·
Mining Help.

Include: OS + version, INTcoin version (intcoin-cli getnetworkinfo),
the exact error, and what you’d already tried.