BitShares Forum

Main => Technical Support => Topic started by: Sammy Noden on November 01, 2017, 12:47:54 am

Title: Failed to broadcast the transaction
Post by: Sammy Noden on November 01, 2017, 12:47:54 am
I've been trying to place orders on the DEX for the last 12 hourse or so, but I keep getting this annoying message:

Failed to broadcast the transaction:
Your transaction has expired without being confirmed, please try again later.

What's going on?
Title: Re: Failed to broadcast the transaction
Post by: Digital Lucifer on November 01, 2017, 01:16:00 am
Please first confirm that in your bitshares wallet/ui

1) Bottom left corner says BITSHARES 171.015
2) Bottom right corner says SYNC (Green writing)

After you confirm both, please go to Settings -> Access and swap to any other node that is UP and please retry again.

Let me know once when you're done.

Cheers,

Luci.
Title: Re: Failed to broadcast the transaction
Post by: Sammy Noden on November 01, 2017, 03:16:52 am
Hi,

Thanks for the tips. Still not working unfortunately.
Title: Re: Failed to broadcast the transaction
Post by: Sammy Noden on November 01, 2017, 03:24:54 am
Currently on:

Hong Kong
wss://openledger.hk/ws
UP
Low latency
Title: Re: Failed to broadcast the transaction
Post by: Digital Lucifer on November 01, 2017, 04:19:14 am
Currently on:

Hong Kong
wss://openledger.hk/ws
UP
Low latency

If Hong Kong for you is low latency, can you try please wss://bitshares.apasia.tech/ws (even if it says down click activate)

I will see on the node probably when you pop in. Problem is transactions are going, because witness are sending to our node transactions, but today 70% of witnesses are having over 1000ms latency towards our node, even usually its under 400ms.

Please let me know on update.

Thanks.

Luci
Title: Re: Failed to broadcast the transaction
Post by: Sammy Noden on November 01, 2017, 07:55:23 am
I can't see that one. The available ones are:

Hong Kong
wss://openledger.hk/ws
UP
Low latency
Available Nodes

Add Node
Choose closest automatically
...
Hong Kong
wss://bit.btsabc.org/ws
UP
Medium latency
Hong Kong
wss://bts.ai.la/ws
UP
High latency
Nuremberg, Germany
wss://bitshares.openledger.info/ws
UP
High latency
Dallas, USA
wss://dexnode.net/ws
UP
High latency
Public Testnet Server (Frankfurt, Germany)
wss://node.testnet.bitshares.eu
Munich, Germany
wss://bitshares.crypto.fans/ws
DOWN
__
China
wss://bitshares-api.wancloud.io/ws
DOWN
__
Hangzhou, China
wss://bitshares.dacplay.org/ws
DOWN
__
Locally hosted
ws://127.0.0.1:8090
DOWN
__
Berlin, Germany
wss://eu.openledger.info/ws
DOWN
__

Anyway, I though low latency was good?
Title: Re: Failed to broadcast the transaction
Post by: Digital Lucifer on November 01, 2017, 04:10:38 pm
I can't see that one. The available ones are:

Hong Kong
wss://openledger.hk/ws
UP
Low latency
Available Nodes

Add Node
Choose closest automatically
...
Hong Kong
wss://bit.btsabc.org/ws
UP
Medium latency
Hong Kong
wss://bts.ai.la/ws
UP
High latency
Nuremberg, Germany
wss://bitshares.openledger.info/ws
UP
High latency
Dallas, USA
wss://dexnode.net/ws
UP
High latency
Public Testnet Server (Frankfurt, Germany)
wss://node.testnet.bitshares.eu
Munich, Germany
wss://bitshares.crypto.fans/ws
DOWN
__
China
wss://bitshares-api.wancloud.io/ws
DOWN
__
Hangzhou, China
wss://bitshares.dacplay.org/ws
DOWN
__
Locally hosted
ws://127.0.0.1:8090
DOWN
__
Berlin, Germany
wss://eu.openledger.info/ws
DOWN
__

Anyway, I though low latency was good?

If the node is out of sync, or for any reason has an error that nobody notice of admin around node, it can be a problem. Switch up between should be ok.

Transactions still going as you can see at the exchange as well (its moving :) ).

Try changing Browser as well, maybe it will help.

Cheers,

Luci
Title: Re: Failed to broadcast the transaction (AGAIN, AND AGAIN, AND AGAIN)
Post by: Sammy Noden on November 08, 2017, 02:20:12 am
Still having this problem. For the two weeks or so that I have been trying to trade on the DEX, most of the time I am unable to. WTF is going on? I thought Bitshares was supposed to be the fastest blockchain out there!

This is what I can see:

bitshares.171102

SYNCHED
head block #21600749
Title: Re: Failed to broadcast the transaction
Post by: fav on November 08, 2017, 05:52:42 am
bitshares has 200k transactions per day, so do you think this issue is a blockchain problem or a user problem?

there are lots of possible problems, so you should start checking your settings.

eg.

bad vpn/firewall?
are you on the testnet for whatever reason?
does your password work?
changed the nodes?
tried another wallet?
Title: Re: Failed to broadcast the transaction
Post by: Sammy Noden on November 08, 2017, 08:50:22 am
bad vpn/firewall? What do you mean by 'bad'? I've never had any problems with my VPN or firewall in the past

are you on the testnet for whatever reason? What do you mean here?

does your password work? Yes

changed the nodes? Yes, many, many times, but shouldn't these kinds of connectivity problems be resolved automatically?! I just want a trading experience that is at least as good as a CEX.

tried another wallet? Are you suggesting that the Bitshares wallet I am using is somehow defective? If so, why? Would you recommend a better wallet? Which one?


In case it is not clear from my previous messages, I have been able to place some orders, but most of the time I have not been able to because of what I suspect are systemic problems / problems with the Bitshares nodes (please refer to the rather abstruse comment above: Problem is transactions are going, because witness are sending to our node transactions, but today 70% of witnesses are having over 1000ms latency towards our node, even usually its under 400ms).
Title: Re: Failed to broadcast the transaction
Post by: fav on November 08, 2017, 08:57:43 am
tried without VPN?
Title: Re: Failed to broadcast the transaction
Post by: Sammy Noden on November 09, 2017, 06:02:05 am
Yes, my VPN has not been switched on will using the DEX. Performance better today despite intermittent YOUR ACTIVE NODE IS OUT OF SYNC messages.