search

Chia-Network / chia-blockchain

Chia blockchain python implementation (full node, farmer, harvester, timelord, and wallet)
Apache License 2.0
10.81k stars 2.02k forks source link

[BUG] : WALLET can't SYNC - connections : 0 #2730

Closed casa10 closed 3 years ago

casa10 commented 3 years ago

Describe the bug

OS : windows 10 pro 64 bits Chia version : 1.1.2

I closed chia gui to switch off computer I start computer and after launch chia gui. He took little time to sync the full node. Farming status became "Farming" Local hovester Plot passed to "farming" BUT Wallet status : not synced Wallet Height :183979 whereas height on full node status equal 185009 Wallet Connections : 0

I looked on debug files and it's written 2021-04-25T20:50:41.869 wallet wallet_server : ERROR Exception: <class 'concurrent.futures._base.CancelledError'>, closing connection {'host': '127.0.0.1', 'port': 8444}. Traceback (most recent call last): File "chia\server\server.py", line 521, in api_call File "asyncio\tasks.py", line 435, in wait_for concurrent.futures._base.CancelledError

Expected behavior I would like to know why this error. Even with restarting chi gui or computer : same problems. Questions :

roybotbot commented 3 years ago

Do you have port forwarding set up on your router? You need to forward port 8444

You can use this site to check if port 8444 is open: https://portchecker.co/

speedmann commented 3 years ago

@royimous thats wrong. You do not need to portforward to be able to sync.

roybotbot commented 3 years ago

@royimous thats wrong. You do not need to portforward to be able to sync.

You're technically right, except, opening port 8444 does solve a lot of the sync issues.

Quoting the chia-blockchain README:

If you are behind a NAT, it can be difficult for peers outside your subnet to reach you when they start up. You can enable UPnP on your router or add a NAT (for IPv4 but not IPv6) and firewall rules to allow TCP port 8444 access to your peer.

Connecting to more peers speeds up the sync and you can help this by opening port 8444.

hoffmang9 commented 3 years ago

@royimous is precisely correct.

However the original issue is something we see in rare cases where the App can't get it's preferred ports. Often that means there are zombie versions and a computer restart is in order on Windows.

casa10 commented 3 years ago

Hye, My port 8444 is opened from beginning. After few restarts, that worked. I don't know if apps is stable.

github-actions[bot] commented 3 years ago

This issue has been flagged as stale as there has been no activity on it in 14 days. If this issue is still affecting you and in need of review, please update it to keep it open.