chia-blockchain: [BUG] Cannot connect to host 127.0.0.1:8444 ssl

The only solution I found is to downgrade the client to version 1.2.7. Seems to be working.

chia stop all -d

git pull
git checkout 1.2.7
sh install.sh

. ./activate
chia start farmer

Can anyone help this a noob figure out how to update my node with #8771 as @emlowe suggested?

Something like this on Linux…

$ git clone -b latest https://github.com/Chia-Network/chia-blockchain.git ./
$ git fetch origin pull/8771/head:pr-8771 && git checkout pr-8771
$ chmod +x install.sh
$ ./install.sh

Just replace 8771 with any PR number…

2021-08-28T14:26:09.221 farmer farmer_server              : INFO     Cannot connect to host 127.0.0.1:8444 ssl:<ssl.SSLContext object at 0x000001DE33472640> [Określona nazwa sieciowa już jest niedostępna]

2021-08-28T14:26:10.219 wallet wallet_server              : INFO     Cannot connect to host 127.0.0.1:8444 ssl:<ssl.SSLContext object at 0x0000023B00DA1640> [Określona nazwa sieciowa już jest niedostępna]

Wallet can’t sync … running since april, stopped yesterday o.O

1.4.0 проблема такая же вы будете ее решать?

The only solution I found is to downgrade the client to version 1.2.7. Seems to be working.

chia stop all -d

git pull
git checkout 1.2.7
sh install.sh

. ./activate
chia start farmer

This got me going again as well. I had to delete the database first though.

@nothingshocking try just starting the node only.

I’ll try that but I need the the wallet to finish sync’ing. If I start only the node that doesn’t support my farm and separate harvester, does it?

Yes, that’s right. Once your node starts up OK, you can start the other services separately. I’d start the harvester first, then farmer, then wallet. See chia start -h for more info.

I’m not exactly sure on the technicality of the works, but depending on the hardware configuration, starting up slowly through manual intervention can make a significant difference.

It will be slow the first time. The idea is the next start should be faster though.

I did a lot of things, and finally after giving this command the node start to work again:

.\chia.exe configure --set-farmer-peer 192.168.1.106:8447

Where 192.168.1.106 must be replaced for your node local IP. I did this trying that node instead of connecting to the IP loopback, it did it to the local IP of the node.

I hope that it works for you too.

I’m experiencing this issue. Anyone have a solution?

Same here. System was hung up today (noticed space pool has almost no space for hours today). Had to reboot the system and now the node will not start. There’s tons of this:

Reconnecting to peer {'host': '127.0.0.1', 'port': 8444}

And netstat shows:

tcp      518      0 127.0.0.1:8444          127.0.0.1:60316         CLOSE_WAIT  -                   
tcp      518      0 127.0.0.1:8444          127.0.0.1:60298         CLOSE_WAIT  -                   
tcp      518      0 127.0.0.1:8444          127.0.0.1:60280         CLOSE_WAIT  -                   
tcp      518      0 127.0.0.1:8444          127.0.0.1:60124         CLOSE_WAIT  -                   
tcp      518      0 127.0.0.1:8444          127.0.0.1:60058         CLOSE_WAIT  -                   
tcp      518      0 127.0.0.1:8444          127.0.0.1:60150         CLOSE_WAIT  -                   
tcp      518      0 127.0.0.1:8444          127.0.0.1:60084         CLOSE_WAIT  -                   
tcp      518      0 127.0.0.1:8444          127.0.0.1:60118         CLOSE_WAIT  -                   
tcp      518      0 127.0.0.1:8444          127.0.0.1:60296         CLOSE_WAIT  -                   
tcp      518      0 127.0.0.1:8444          127.0.0.1:60320         CLOSE_WAIT  -  

There’s probably 50-60 of those.

I tried restarting just the node and got a trace back.

OSError: [Errno 98] error while attempting to bind on address ('::', 8444, 0, 0): address already in use

Netstat did say chia_full_node running on ::8444 though. Even after trying chia stop all -d and restarting.

Just restarted again, tried chia start farmer:

OSError: [Errno 99] error while attempting to bind on address ('::1', 55400, 0, 0): cannot assign requested address

Nothing is on that port. And I’ve got IPv6 disabled. This is a Debian 10 virtual machine. Not seeing any hardware or journalctl errors. It looks like this is only attempting IPv6? That’s can’t be right?

Edit: I was able to get the node started finally. I edited /etc/hosts and commented:

#::1     localhost ip6-localhost ip6-loopback

then the node would stop trying to use IPv6. Now the node looks like ok, but nothing is farming yet. Probably needs to sync. I’m not sure what happened with the crash except after reboot I saw in the debug log many many lines about mempool. The last log entries looked like this:

2021-09-27T13:06:54.613 full_node chia.full_node.mempool_manager: INFO     It took 0.002203226089477539 to pre validate transaction
2021-09-27T13:06:54.620 full_node chia.full_node.mempool_manager: INFO     add_spendbundle took 0.006319761276245117 seconds, cost 10772850 (0.098%)
2021-09-27T13:06:54.666 full_node chia.full_node.mempool_manager: INFO     It took 0.002131223678588867 to pre validate transaction
2021-09-27T13:06:54.673 full_node chia.full_node.mempool_manager: INFO     add_spendbundle took 0.0063669681549072266 seconds, cost 10772852 (0.098%)
2021-09-27T13:06:57.388 full_node chia.full_node.mempool_manager: INFO     It took 0.01028895378112793 to pre validate transaction
2021-09-27T13:06:57.402 full_node chia.full_node.mempool_manager: INFO     add_spendbundle took 0.012296199798583984 seconds, cost 10772852 (0.098%)
2021-09-27T13:06:57.433 full_node chia.full_node.mempool_manager: INFO     It took 0.0038022994995117188 to pre validate transaction
2021-09-27T13:06:57.444 full_node chia.full_node.mempool_manager: INFO     add_spendbundle took 0.010668516159057617 seconds, cost 10772850 (0.098%)
2021-09-27T13:07:00.071 full_node chia.full_node.mempool_manager: INFO     It took 0.005041837692260742 to pre validate transaction
2021-09-27T13:07:00.080 full_node chia.full_node.mempool_manager: INFO     add_spendbundle took 0.008687019348144531 seconds, cost 10772850 (0.098%)
2021-09-27T13:07:00.141 full_node chia.full_node.mempool_manager: INFO     It took 0.005942583084106445 to pre validate transaction
2021-09-27T13:07:00.151 full_node chia.full_node.mempool_manager: INFO     add_spendbundle took 0.009321451187133789 seconds, cost 10772852 (0.098%)
2021-09-27T13:07:00.987 full_node chia.full_node.full_node: INFO     ⏲️  Finished signage point 4/64: CC: e271a18355ff116df049f2d4084d8df4310d5589cdd931dd385449105322ab7c RC: 5d1fc94b212de90f3f1bda4f99f0eaea159ce01f6a6bf6e81d7$

There were a lot more mempool_manager log entries all day in the logs. Not sure if any of this is helpful. I’m blaming something on my end.

I have the same issue. I used to use client 1.1.7 Yesterday updated the cliënt to 1.2.7. Since then my wallet is not able to sync and shows 0 xch. The log continuesly showing “Cannot connect to host 127.0.0.1:8444”. Local firewall temporarly disabled to see if it helped. It makes no difference. “Wallet Status: Not Synced (0)”