| 1 |
--- |
| 2 |
title: "Help: Failed transaction" |
| 3 |
nav_title: Failed transaction |
| 4 |
category: troubleshooting |
| 5 |
--- |
| 6 |
|
| 7 |
Use this guide if an outgoing transaction shows status "Failed" in the **History** tab. |
| 8 |
|
| 9 |
Right-click on the failed transaction **→ Resend transaction**. Click **Broadcast** to submit the transaction to the selected node. |
| 10 |
|
| 11 |
Check a block explorer (e.g. [xmrchain.net](https://xmrchain.net/txpool)) to verify that the transaction has reached the transaction pool. Try resending the transaction using a different node if it does not show up within a few minutes. |
| 12 |
|
| 13 |
### Cause |
| 14 |
|
| 15 |
A failed transaction is caused by a node's failure to relay your transaction to the Monero network. This can happen when the node you are connected to is misconfigured or poorly connected. |
| 16 |
|
| 17 |
Relay failures are common in nodes that are configured with `--tx-proxy`, for this reason it is recommended to disable this option on publicly accessible nodes. |
| 18 |
|
| 19 |
### Local node |
| 20 |
|
| 21 |
If you are connected to a local node, you can alternatively manually relay the transaction by running the following command in the daemon console: |
| 22 |
|
| 23 |
``` |
| 24 |
relay_tx <txid> |
| 25 |
``` |
| 26 |
For example: |
| 27 |
``` |
| 28 |
relay_tx 210557aa553718f8faced109768c54763702847e52f66f9ebdee7aceee90c4bc |
| 29 |
``` |
| 30 |
|
| 31 |
If `monerod` is daemonized you can run: |
| 32 |
|
| 33 |
``` |
| 34 |
monerod relay_tx <txid> |
| 35 |
``` |
| 36 |
|
| 37 |
or via the JSON RPC with `curl`: |
| 38 |
|
| 39 |
``` |
| 40 |
curl http://127.0.0.1:18081/json_rpc -d \ |
| 41 |
'{"jsonrpc":"2.0", \ |
| 42 |
"id":"0", \ |
| 43 |
"method":"relay_tx", \ |
| 44 |
"params":{"txids":["TXID_HERE"]}}' \ |
| 45 |
-H 'Content-Type: application/json' |
| 46 |
``` |
| 47 |
|
| 48 |
Replace `TXID_HERE` with the actual txid. |