Author Topic: Failed to sync with the API server  (Read 11357 times)

0 Members and 1 Guest are viewing this topic.

Offline MrJeans

  • Hero Member
  • *****
  • Posts: 599
    • View Profile
  • BitShares: mrjeans
When cloning the github and running the client on a local host:
The client is very slow in general
The exchange is non functional (just shows as loading continuously).

Tried connecting to different servers.
Is there any way to fix this so that testing can be done locally.

Offline ebit

  • Committee member
  • Hero Member
  • *
  • Posts: 1905
    • View Profile
  • BitShares: ebit
Quote
国内近日已新增以下 API 服务器节点,使用网页钱包和轻钱包的可以自行添加:
● wss://bit.btsabc.org/ws (比特股中文网 @吴序强 提供)
● wss://bts.transwiser.com/ws (易转网 @巨蟹 提供)
● wss://freedom.bts123.cc:15138 (著名的黑粉 @惨 提供)
● wss://okbtc.org:8089/ws (bebtc.com 的 @郑浩 提供)
● wss://ratebts.com:8089(@AJ 提供)
● wss://openledger.hk/ws (OpenLedger 香港提供)

Have a try
telegram:ebit521
https://weibo.com/ebiter

Offline Mateusz

  • Newbie
  • *
  • Posts: 17
    • View Profile
After updating the API connection menu showed up. Many thanks!

Offline nmywn

  • Sr. Member
  • ****
  • Posts: 266
    • View Profile


Chose this one.
I had the same problem today, but this has nothing to do with my clock. Now it's ok, but still far from perfect. New servers are ready to go, but we must wait for official release, which should happen very soon.
BTW new client is 160829.

Offline Mateusz

  • Newbie
  • *
  • Posts: 17
    • View Profile
I recently downloaded the new BitShares 2.0.160813 light software and set up my account. All seamed to be working flawlessly until yesterday when I tried to start the client and got the following screen:

Quote
Failed to sync with the API server
Please verify that your computer clock is correct.
Once you've synchronized your clock, please refresh this page.

I live in the UTC+1 time zone and use Windows 7 x64 with clock automatically synchronized with 'time.windows.com'. I've synced the computer clock and restarted the client multiple times but the problem persists. How do I change API server or otherwise resolve this error?