Author Topic: Error Message - Failed to broadcast  (Read 1256 times)

0 Members and 1 Guest are viewing this topic.

Offline mike623317

  • Hero Member
  • *****
  • Posts: 637
    • View Profile
Error Message - Failed to broadcast
« on: November 10, 2017, 10:05:50 pm »

Does anyone know what this means?

Transaction was not signed. Do you have a private key? [no_signers]. 

Thanks


Offline mf-tzo

  • Hero Member
  • *****
  • Posts: 1725
    • View Profile
Re: Error Message - Failed to broadcast
« Reply #1 on: November 11, 2017, 11:05:29 am »
I think that means that for the account you are trying to transfer you have put multi-sig security and the transaction needs to be signed by the other permitted accounts. I get the same error in GUI.

However I have no idea how to sign from the other account in GUI so the transaction can be processed. If this is not possible in GUI but only in CLI then multi-sig permissions should be removed from GUI. If it is possible someone should make an ELI5 for GUI users..

Offline random

  • Newbie
  • *
  • Posts: 7
    • View Profile
Re: Error Message - Failed to broadcast
« Reply #2 on: November 18, 2017, 10:01:01 pm »
I think the error is lag related.
As I posted in the first message I wrote. I have no low latency nodes available and I get this message regularly.
I believe it is the 3 second block timing out before the request is recieved.
Regards,

Offline Sammy Noden

  • Newbie
  • *
  • Posts: 13
    • View Profile
Re: Error Message - Failed to broadcast
« Reply #3 on: November 20, 2017, 03:12:29 am »
I've been having the same problem since I started trying to using Bitshares DEX a few weeks ago. Currently 7 (!) nodes are down, 1 is showing neither up nor down (Public Testnet Server) and only 3 are up, but they all have low latency. One again the DEX is completely unusable!

Offline fav

  • Administrator
  • Hero Member
  • *****
  • Posts: 4278
  • No Pain, No Gain
    • View Profile
    • Follow Me!
  • BitShares: fav
Re: Error Message - Failed to broadcast
« Reply #4 on: November 20, 2017, 11:41:18 am »
I've been having the same problem since I started trying to using Bitshares DEX a few weeks ago. Currently 7 (!) nodes are down, 1 is showing neither up nor down (Public Testnet Server) and only 3 are up, but they all have low latency. One again the DEX is completely unusable!

they are not down, it just took your browser to long to ping them, basically.

check if you're using a bad VPN or firewall. if not, then just connect to one that's shown as down. it'll work.

or try with an alternative wallet

I use DEX every day, and give a lot of support. most of the times it's a local issue

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4538
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
Re: Error Message - Failed to broadcast
« Reply #5 on: November 20, 2017, 07:54:13 pm »
I think that means that for the account you are trying to transfer you have put multi-sig security and the transaction needs to be signed by the other permitted accounts. I get the same error in GUI.

However I have no idea how to sign from the other account in GUI so the transaction can be processed. If this is not possible in GUI but only in CLI then multi-sig permissions should be removed from GUI. If it is possible someone should make an ELI5 for GUI users..
Transferring from multisig accounts is possible in the GUI with the "propose" feature. The parties can approve the proposal in the GUI. That feature has been in GUI for more than a year.

As a user who has used BitShares for a long time (I think you are, since you are a hero member of this forum) you should be able to figure it out, perhaps with help from other users. That "someone" that should make an ELI5 can be YOU.
BTS account: abit
BTS committee member: abit
BTS witness: in.abit