BitShares Forum
Main => Technical Support => Topic started by: jbperez808 on June 29, 2017, 06:30:30 pm
-
When running my self-compiled witness_node (the process of which also had certain issues I had to tediously correct manually) and pointing the Bitshares Light Client to it, I get a "Failed to sync with the API server" message.
The computer clocks are correct.
How do I fix this?
Is the message showing up because the blockchain has yet to sync to the latest available blocks?
-
When running my self-compiled witness_node (the process of which also had certain issues I had to tediously correct manually) and pointing the Bitshares Light Client to it, I get a "Failed to sync with the API server" message.
The computer clocks are correct.
How do I fix this?
Is the message showing up because the blockchain has yet to sync to the latest available blocks?
Wait till your node syncs with the network then when you open your Light Wallet you should see an output from your node that it has opened a new DB or something similar. That way you will know that you connected to your node.
-
Ok, looks like I had to wait till the entire blockchain was synced before the "Failed to sync with the API server" goes away.
I think it would be good if that error message was modified to aid newbies who aren't sure what's going on.
-
Hi, I'm also new here having a similar problem!
I installed the bitshares application about a week ago and so far everything was fine. When I opened bitshares2-light this morning everything was still working fine. I even did some transactions.
Until a few hours later when I was logged in to a VPN client, I got that "Failed to sync with the API server" screen. I closed the VPN, tried different Wifi's, tried different API Servers, tried reset settings, I synced my clock, restarted my laptop, nothing is working. I'm having this problem for a couple of hours now. One API (Public Testnet Server (Frankfurt, Germany)) did open the application, but not my account and functions like exchange were not available. I could only set up a new account.
I also read the thread about this problem from about a year ago https://bitsharestalk.org/index.php?topic=23273.0 (https://bitsharestalk.org/index.php?topic=23273.0), but I couldn't get anything useful out of it. I'm not a Techie so I don't understand all of it...
And now the application opens again after some time of loading, but not with my account. I can only create a new one or sign it with a password, but since there's no account loaded it doesn't recognise my account name...
I'm glad for any help! Thank you.
-
I'm also having the same problem now. None of the listed Full Node API servers are working. All are giving the "failed to sync with the API" error message.
It looks like https://bitshares.org/wallet has the same problem...
UPDATE: Hmm... very annoying...
I had to adjust date/time on my Windows machine by turning off "set time automatically" then turning it on again...
It then started working again.
-
https://steemit.com/bitshares/@ash/bitshares-entered-unplanned-maintenance-mode
-
I'm also having the same problem now. None of the listed Full Node API servers are working. All are giving the "failed to sync with the API" error message.
There was an issue with the network couple hours ago. It's coming back up, my FULL node is being rebuild and should be back up shortly.
-
Ok, I hope it'll work again soon!
It now looks like this:
(https://preview.ibb.co/iK5gPa/screenshot_140.png)
-
Ok was working again! After I hit retry about 5 times, but i can't log in, incorrect pw...
-
Stopped working on my end, now failing to sync again. :(
-
Stopped working on my end, now failing to sync again. :(
Same here! I can open it though by clicking on retry 10times or more, but can't log in then :-\
-
Stopped working on my end, now failing to sync again. :(
Same here! I can open it though by clicking on retry 10times or more, but can't log in then :-\
select another API node
-
Stopped working on my end, now failing to sync again. :(
Same here! I can open it though by clicking on retry 10times or more, but can't log in then :-\
select another API node
Thank you! It's been working fine since this morning, without me doing anything.