Armory tx broadcast timed out on version 0.96

[keithlovett]

So I waited months for this version to be released so I could finally send bitcoin. No problem accepting them though. With prior versions I was unable to send even after replacing core, updating to emergency release before this.

I am attaching my log. Hope someone can help. Otherwise sounds like a case of very dogged perseverance.
armorylog_20170517_1310.txt

[achow101]

Try the 0.96.1 testing build: https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.0.1-testing

What version of Core are you using?

[keithlovett]

[Hey achow.

Thx for response. Apologies for delay responding. I still can't send any coin. Same timeout msg. I'm already using Bitcoin Core 0.14.2. and Armory 0.96.1 testing build.

I haven't been able to use wallet for over a month now and just want to recover my coins.
Shall I update to v0.96.0.4-testing? or keep waiting for a proper release?

Thanks guys.

[achow101]

Update to 0.96.1 final release: https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.1. If you are already using 0.96.0.4-testing, that's fine too as they are functionally the same.

[keithlovett]

OK. All done and at least problem is different. On trying to send funds I receive a warning asking if I'm sure I want to proceed as fee rate of 113 is below recommended 200 satoshi. It also recommends I turn on RPC?

That's all I get..

Advice anyone please? Log attached:

armorylog_20170728_1729.txt

[achow101]

It's a warning, not an error. You can ignore the warning and continue. The default fee rate (and the low fee rate warning threshold) was set when the fee rate was much higher, but it has significantly dropped since then. You should also enable RPC on Bitcoin Core if you have not already. Add server=1 to your bitcoin.conf file and restart Core. Enabling RPC will make sure your transaction is actually broadcast and allow you to get fee estimates from Core.

[keithlovett]

Thanks for prompt response achow! I tried ignoring warning but could still not send coins.
I'll enable RPC on Bitcoin core and see if that makes the difference,
Keith

[keithlovett]

I can't find my bitcoin.conf file. Do I have to compile it myself? Running Windows 10. Can you help once more achow?

[goatpig]

Create it in the notepad if you don't have one. Save it in your Bitcoin datadir.

[keithlovett]

Hey goatpig. Does this look OK? Only amendment I've made is to add server.1 but I imagine I have to do more. Saved in bitcoin datadir.

> ### ##
> ## bitcoin.conf configuration file. Lines beginning with # are comments.
> ##
>  
> # Network-related settings:
> 
> # Run on the test network instead of the real bitcoin network.
> #testnet=0
> 
> # Run a regression test network
> #regtest=0
> 
> # Connect via a SOCKS5 proxy
> #proxy=127.0.0.1:9050
> 
> # Bind to given address and always listen on it. Use [host]:port notation for IPv6
> #bind=<addr>
> 
> # Bind to given address and whitelist peers connecting to it. Use [host]:port notation for IPv6
> #whitebind=<addr>
> 
> ##############################################################
> ##            Quick Primer on addnode vs connect            ##
> ##  Let's say for instance you use addnode=4.2.2.4          ##
> ##  addnode will connect you to and tell you about the      ##
> ##    nodes connected to 4.2.2.4.  In addition it will tell ##
> ##    the other nodes connected to it that you exist so     ##
> ##    they can connect to you.                              ##
> ##  connect will not do the above when you 'connect' to it. ##
> ##    It will *only* connect you to 4.2.2.4 and no one else.##
> ##                                                          ##
> ##  So if you're behind a firewall, or have other problems  ##
> ##  finding nodes, add some using 'addnode'.                ##
> ##                                                          ##
> ##  If you want to stay private, use 'connect' to only      ##
> ##  connect to "trusted" nodes.                             ##
> ##                                                          ##
> ##  If you run multiple nodes on a LAN, there's no need for ##
> ##  all of them to open lots of connections.  Instead       ##
> ##  'connect' them all to one node that is port forwarded   ##
> ##  and has lots of connections.                            ##
> ##       Thanks goes to [Noodle] on Freenode.               ##
> ##############################################################
> 
> # Use as many addnode= settings as you like to connect to specific peers
> #addnode=69.164.218.197
> #addnode=10.0.0.2:8333
> 
> # Alternatively use as many connect= settings as you like to connect ONLY to specific peers
> #connect=69.164.218.197
> #connect=10.0.0.1:8333
> 
> # Listening mode, enabled by default except when 'connect' is being used
> #listen=1
> 
> # Maximum number of inbound+outbound connections.
> #maxconnections=
> 
> #
> # JSON-RPC options (for controlling a running Bitcoin/bitcoind process)
> #
> 
>  server=1 tells Bitcoin-Qt and bitcoind to accept JSON-RPC commands
> #server=0
> 
> # Bind to given address to listen for JSON-RPC connections. Use [host]:port notation for IPv6.
> # This option can be specified multiple times (default: bind to all interfaces)
> #rpcbind=<addr>
> 
> # If no rpcpassword is set, rpc cookie auth is sought. The default `-rpccookiefile` name
> # is .cookie and found in the `-datadir` being used for bitcoind. This option is typically used
> # when the server and client are run as the same user.
> #
> # If not, you must set rpcuser and rpcpassword to secure the JSON-RPC api. The first
> # method(DEPRECATED) is to set this pair for the server and client:
> #rpcuser=Ulysseys
> #rpcpassword=YourSuperGreatPasswordNumber_DO_NOT_USE_THIS_OR_YOU_WILL_GET_ROBBED_385593
> #
> # The second method `rpcauth` can be added to server startup argument. It is set at intialization time
> # using the output from the script in share/rpcuser/rpcuser.py after providing a username:
> #
> # ./share/rpcuser/rpcuser.py alice
> # String to be appended to bitcoin.conf:
> # rpcauth=alice:f7efda5c189b999524f151318c0c86$d5b51b3beffbc02b724e5d095828e0bc8b2456e9ac8757ae3211a5d9b16a22ae
> # Your password:
> # DONT_USE_THIS_YOU_WILL_GET_ROBBED_8ak1gI25KFTvjovL3gAM967mies3E=
> #
> # On client-side, you add the normal user/password pair to send commands:
> #rpcuser=alice
> #rpcpassword=DONT_USE_THIS_YOU_WILL_GET_ROBBED_8ak1gI25KFTvjovL3gAM967mies3E=
> #
> # You can even add multiple entries of these to the server conf file, and client can use any of them:
> # rpcauth=bob:b2dd077cb54591a2f3139e69a897ac$4e71f08d48b4347cf8eff3815c0e25ae2e9a4340474079f55705f40574f4ec99
> 
> # How many seconds bitcoin will wait for a complete RPC HTTP request.
> # after the HTTP connection is established. 
> #rpcclienttimeout=30
> 
> # By default, only RPC connections from localhost are allowed.
> # Specify as many rpcallowip= settings as you like to allow connections from other hosts,
> # either as a single IPv4/IPv6 or with a subnet specification.
> 
> # NOTE: opening up the RPC port to hosts outside your local trusted network is NOT RECOMMENDED,
> # because the rpcpassword is transmitted over the network unencrypted.
> 
> # server=1 tells Bitcoin-Qt to accept JSON-RPC commands.
> # it is also read by bitcoind to determine if RPC should be enabled 
> #rpcallowip=10.1.1.34/255.255.255.0
> #rpcallowip=1.2.3.4/24
> #rpcallowip=2001:db8:85a3:0:0:8a2e:370:7334/96
> 
> # Listen for RPC connections on this TCP port:
> #rpcport=8332
> 
> # You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind
> # running on another host using this option:
> #rpcconnect=127.0.0.1
> 
> # Create transactions that have enough fees so they are likely to begin confirmation within n blocks (default: 6).
> # This setting is over-ridden by the -paytxfee option.
> #txconfirmtarget=n
> 
> # Miscellaneous options
> 
> # Pre-generate this many public/private key pairs, so wallet backups will be valid for
> # both prior transactions and several dozen future transactions.
> #keypool=100
> 
> # Pay an optional transaction fee every time you send bitcoins.  Transactions with fees
> # are more likely than free transactions to be included in generated blocks, so may
> # be validated sooner.
> #paytxfee=0.00
> 
> # Enable pruning to reduce storage requirements by deleting old blocks. 
> # This mode is incompatible with -txindex and -rescan.
> # 0 = default (no pruning).
> # 1 = allows manual pruning via RPC.
> # >=550 = target to stay under in MiB. 
> #prune=550
> 
> # User interface options
> 
> # Start Bitcoin minimized
> #min=1
> 
> # Minimize to the system tray
> #minimizetotray=1

[achow101]

That's fine. But please don't paste config files without putting in code format blocks, you're making it harder to read since Markdown is rendering it.

[keithlovett]

Sorry about that guys. Will remember next time. & will let you know how I get on - manana!.
Thanks for all your support today.

[goatpig]

I fixed the post. The only thing you need is the server=1 line.

[keithlovett]

Great stuff goatpig. Ty.

[goatpig]

Update to 0.96.1

[keithlovett]

OK Guys.
I jumped the gun. I'm still getting same problem.
First I get the fees warning but proceed proceed anyway. Then I get second panel confirming transaction timed out,
RPC interface of node disabled . . . enable RPC and try again.

I've tried on pre-release and now have 0.96.1 installed.
The only line I changed on .conf file was:

server=1 tells Bitcoin-Qt and bitcoind to accept JSON-RPC commands
Still kept it in datadir,

[keithlovett]

As well as above reference to server1 there' also this one that I'd missed:
server=1 tells Bitcoin-Qt to accept JSON-RPC commands.
Should this be included in .conf file?

[keithlovett]

Guys. I'm so sorry for using this space but I honestly don't even have enough accessible bitcoin to enable me to post on forum at bitcointalk!

I've now noticed I've received no deposits from my miner for almost 2 months. They had been arriving in Armory regularly even when I couldn't send so I'm not sure if fault lies with them or with the wallet.
I'd really appreciate your support guys. As I said I can't resolve mining issue until wallet is fixed and can't access community support..
Thanks for your patience, Keith

[keithlovett]

Also I'm stuck at 671661 blocks which would account for prob with recent deposits.

[baselbers]

#231
#295

[tril0byte]

Workaround: if you can't transmit from armory, before trying to broadcast, go to transaction details and copy the transaction to your clipboard or a text document. Then if broadcast doesn't work, paste the raw tx into the command line of: bitcoin-cli sendrawtransaction

[keithlovett]

Fresh up-to-date installation works perfectly on laptop , but same Armory 0.96 set-up on Desktop won't recognise full Blockchain & tx broadcast always times out so I'm going for a fresh installation.

…

On 5 September 2017 at 17:02, tril0byte ***@***.***> wrote: Workaround: if you can't transmit from armory, before trying to broadcast, go to transaction details and copy the transaction to your clipboard or a text document. Then if broadcast doesn't work, paste the raw tx into the command line of: bitcoin-cli sendrawtransaction — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#225 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEP9xs2__lk8-Ldlx1G-OijpNoh8VTFNks5sfXCcgaJpZM4Ndy1L> .

--