just can’t sync, why!!!
Hey there, are you asking for help or are you venting?
When you ask for help, it’s useful to state what the problem is with some detail. There are thousands of ways computers can be configured so a general “it’s not working” isn’t enough info.
Anyway, do what this guide says: Resolving Sync Issues Port 8444 · Chia-Network/chia-blockchain Wiki · GitHub
please help me, many thanks, lastest log are as follows:
2021-05-05T13:35:27.610 full_node chia.rpc.rpc_server : WARNING Error while handling message: Traceback (most recent call last):
File "chia\rpc\rpc_server.py", line 212, in safe_handle
File "chia\rpc\rpc_server.py", line 200, in ws_api
File "chia\rpc\rpc_server.py", line 161, in open_connection
ValueError: Start client failed, or server is not set
2021-05-05T13:38:47.585 full_node full_node_server : ERROR Exception , exception Stack: Traceback (most recent call last):
File "chia\server\server.py", line 356, in start_client
File "aiohttp\client.py", line 763, in _ws_connect
File "aiohttp\client.py", line 521, in _request
File "aiohttp\connector.py", line 535, in connect
File "aiohttp\connector.py", line 892, in _create_connection
File "aiohttp\connector.py", line 1032, in _create_direct_connection
File "aiohttp\connector.py", line 969, in _wrap_create_connection
File "asyncio\base_events.py", line 949, in create_connection
File "asyncio\selector_events.py", line 473, in sock_connect
concurrent.futures._base.CancelledError
dear all, i can’t sync yet since 3 days ago, got these log, please help.
2021-05-05T13:35:27.610 full_node chia.rpc.rpc_server : WARNING Error while handling message: Traceback (most recent call last):
File "chia\rpc\rpc_server.py", line 212, in safe_handle
File "chia\rpc\rpc_server.py", line 200, in ws_api
File "chia\rpc\rpc_server.py", line 161, in open_connection
ValueError: Start client failed, or server is not set
2021-05-05T13:38:47.585 full_node full_node_server : ERROR Exception , exception Stack: Traceback (most recent call last):
File "chia\server\server.py", line 356, in start_client
File "aiohttp\client.py", line 763, in _ws_connect
File "aiohttp\client.py", line 521, in _request
File "aiohttp\connector.py", line 535, in connect
File "aiohttp\connector.py", line 892, in _create_connection
File "aiohttp\connector.py", line 1032, in _create_direct_connection
File "aiohttp\connector.py", line 969, in _wrap_create_connection
File "asyncio\base_events.py", line 949, in create_connection
File "asyncio\selector_events.py", line 473, in sock_connect
concurrent.futures._base.CancelledError
Update to 1.1.4. It just came out.
yes, this log comes out just from 1.1.4
i got port forwarded, and tested with the open status, the port should be fine i think
the connection status is connected, the wallet is connected, just not sync all the time. please give some help, thanks a lot, it’s being for days like this.
@tim I merged your topics, please don’t start multiple topics with the same information.
@roybot and @Blueoxx have given you links to try and help you solve your problems, if you need additional help then describe what you’ve done and what you experienced, maybe someone will have an idea that is not already covered in those links.
The only thing I can add is: be patient, keep adding introducers and don’t shut down the GUI, it can take quite a few attempts before something starts happening, if you close the GUI, you have to start from scratch, it will take longer.
thanks a lot, and sorry about these. i got it done by changing to another router, and finally found that it was the router’s complicated configuration on the firewall itself, after changed to a simple one, set up the port forwarding, then everything was going fine.
now, it starts syncing, and will be farming again maybe tomorrow morning. many thanks for the reply.
Im using windows and I stumbled on the same problem… The solution is simple.
1.) Open Windows Defender firewall settings
2.) Click advance settings
3.) Right click Inbound rules
4.) Create new rule
5.) Select port
6.) Select both TCP and specific local ports
7.) type 8444 on box
Same process for Outbound rules.