Transaction rejected by our node. Reason: Transaction was previously accepted...

[tomahawkeer]

I have some coins in limbo, and have been since 10/30.

I checked blockchain.info page with the transaction info, and the page now returns the following error:

Transaction rejected by our node. Reason: Transaction was previously accepted but has been pruned from our database

Here is the transaction ID:

8367c64af6d1387a321737041d72a8e1efebd6fbcdafd5993ac4769fde1ec055-000

The transaction amount is actually .2 BTC so its not a huge amount of money but at the same time, it isnt dust.

How do I get my coins back, because it never made it to my other account?

[achow101]

The fee was probably too low so blockchain.info dropped it. My node also does not have your transaction.

You can delete the transaction from your wallet and resend the transaction. Right click the transaction in the transaction list and choose "Abandon transaction". You should then be able to spend the same inputs that that transaction spent.

[tomahawkeer]

The fee was probably too low so blockchain.info dropped it. My node also does not have your transaction.

You can delete the transaction from your wallet and resend the transaction. Right click the transaction in the transaction list and choose "Abandon transaction". You should then be able to spend the same inputs that that transaction spent.

That option is greyed out and not selectable.

[achow101]

That option is greyed out and not selectable.

Restart Bitcoin Core with the -zapwallettxes option. See https://achow101.com/2016/07/Bitcoin-Core-Troubleshooting#option-startup for help with that. It will clear all unconfirmed transaction from your wallet so that you can respend the same inputs.

[tomahawkeer]

That option is greyed out and not selectable.

Restart Bitcoin Core with the -zapwallettxes option. See https://achow101.com/2016/07/Bitcoin-Core-Troubleshooting#option-startup for help with that. It will clear all unconfirmed transaction from your wallet so that you can respend the same inputs.

Cool that fixed it. Will have to remember that if it happens again.