BitShares Forum

Main => General Discussion => Topic started by: logxing on October 14, 2015, 02:34:45 pm

Title: import keys last step, transaction broadcast failed : now <= trx.expiration
Post by: logxing on October 14, 2015, 02:34:45 pm

reason?  :(

Title: Re: import keys last step, transaction broadcast failed : now <= trx.expiration
Post by: betax on October 14, 2015, 02:46:21 pm

I had this issue several times on testnet but it seemed to have disappeared now.

Title: Re: import keys last step, transaction broadcast failed : now <= trx.expiration
Post by: betax on October 14, 2015, 02:46:52 pm

Have you tried other browsers?

Title: Re: import keys last step, transaction broadcast failed : now <= trx.expiration
Post by: wallace on October 14, 2015, 07:14:54 pm

re-broadcast again and again till it succeed

Title: Re: import keys last step, transaction broadcast failed : now <= trx.expiration
Post by: clayop on October 14, 2015, 07:21:57 pm

Is your clock correct? Re-sync your clock.

Title: Re: import keys last step, transaction broadcast failed : now <= trx.expiration
Post by: donkeypong on October 14, 2015, 07:52:33 pm

You mean the system clock?

Title: Re: import keys last step, transaction broadcast failed : now <= trx.expiration
Post by: clayop on October 14, 2015, 07:53:55 pm

Quote from: donkeypong on October 14, 2015, 07:52:33 pm

You mean the system clock?

yes

Title: Re: import keys last step, transaction broadcast failed : now <= trx.expiration
Post by: donkeypong on October 14, 2015, 08:34:03 pm

Thanks for the tip. That's funny. My clock is set to update automatically, but every time I re-synch it manually, my imports or transfers go through successfully for a little while. Then they stop working again with the same error code. And after I manually re-synch, they work again for the next few minutes. Strange quirk, but thank you, it does help.

Title: Re: import keys last step, transaction broadcast failed : now <= trx.expiration
Post by: TheLostBoy on October 14, 2015, 09:18:05 pm

Quote from: logxing on October 14, 2015, 02:34:45 pm

reason?  :(

The answer is here:
https://bitsharestalk.org/index.php/topic,18988.0.html

I think some of us found out an important and annoying issue, and it should be highlighted somewhere.
Most of you, experienced geeks, use linux, so mostly Firefox but the average user is getting errors with either IE and Chrome in Windows, using the light wallet and/or OpenLedger

Title: Re: import keys last step, transaction broadcast failed : now <= trx.expiration
Post by: donkeypong on October 14, 2015, 09:33:29 pm

Quote from: TheLostBoy on October 14, 2015, 09:18:05 pm

I think some of us found out an important and annoying issue, and it should be highlighted somewhere.
Most of you, experienced geeks, use linux, so mostly Firefox but the average user is getting errors with either IE and Chrome in Windows, using the light wallet and/or OpenLedger

Agreed. I'm about as non-technical as anyone here. Initially, I had a lot of trouble with the wallet in windows 10 and with OpenLedger in all three browsers. But Clayyop's tip about the clock really helped. When I finally got it working, let me tell you, this BitShares is a beautiful thing...worth the wait! Kudos to Dan and the team for some terrific work, and I'm sure the GUI stuff will continue to be addressed in the near future. Can't wait for the referral program and to see these other businesses power themselves on this chain.