AMMOcoin Troubleshooting Guide

Node Won't Sync

• Make sure your ammocoin.conf contains addnode entries pointing to the seed nodes: seed1.ammocoin.org (78.141.194.140) seed2.ammocoin.org (104.238.165.56) and seed3.ammocoin.org (207.246.95.210, 45.76.116.97, 144.202.79.114).
• Verify that port 37020 (P2P) is open in your firewall and forwarded on your router if behind NAT.
• Check your connection count: ammocoin-cli getconnectioncount. If it returns 0, your node cannot reach the network.

v1.1.1 Node Sees No Peers

• v1.1.1 uses a new network ID and does not connect to v1.0 or v1.1.0 nodes. Make sure every node you addnode to is also running v1.1.1.
• v1.1.1 reads its config from the new data folder (~/.ammocoin11 on Linux). A config left in the old ~/.ammocoin folder is not used.

"Cannot find the Sapling parameters"

• The node looks for its Sapling parameters in ~/.ammocoin-params (Linux), which depends on HOME. A systemd service often runs without HOME set: add Environment=HOME=/root (or the home folder of the user that runs the node) to the [Service] section, then sudo systemctl daemon-reload and restart. See the example service.

Linux Binary Won't Start (GLIBC errors)

• The v1.1.1 Linux binaries need glibc 2.34 or newer: Ubuntu 22.04 or newer (24.04 tested). Ubuntu 18.04 and 20.04 cannot run them. Upgrade the OS.

Masternode Won't Start

• Masternodes must use port 37020 on a public, routable IP. Check masternodeaddr=IP:37020 and externalip=IP on the server and the IP:port in masternode.conf on the controller wallet.
• The collateral needs exactly 10,000 AMMO in one output with at least 15 confirmations. Check with getmasternodeoutputs, then getmasternodestatus on the server.

RPC Connection Refused

• Confirm that rpcuser and rpcpassword are set in your ammocoin.conf and match what you pass to ammocoin-cli.
• Ensure the daemon is actually running: ps aux | grep ammocoind.
• Check that rpcport (default 51473) is not blocked by a local firewall.

Windows SmartScreen or macOS Gatekeeper Blocks the App

The Windows and Linux binaries are not code-signed. On Windows, SmartScreen may warn you: verify the checksum, then choose "More info" > "Run anyway". The v1.1.1 macOS downloads are signed and notarized by Apple, so Gatekeeper should open them; an app you built yourself is not signed, and Gatekeeper may refuse to open it. Two solutions on macOS:

• Right-click method: Right-click (or Control-click) the app and choose Open. Confirm the dialog.
• Terminal method: Run xattr -r -d com.apple.quarantine /path/to/AMMOcoin-Qt.app to remove the quarantine flag.

Still Stuck?

If none of the above resolves your issue, please open an issue on the GitHub Issues page with details about your operating system, AMMOcoin version, and the exact error message.