search

Chia-Network / chia-blockchain

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

[BUG] Errors connecting to wallet: ECONNREFUSED on local host #3869

Closed fritol closed 3 years ago

fritol commented 3 years ago

Connecting to wallet

running in a loop no network traffic in the dev console:

events.js:292 Uncaught Error: connect ECONNREFUSED 127.0.0.1:55400 at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141) main.js:1 Already connected, not reconnecting. main.js:1 0 main.js:1 Already connected, not reconnecting. main.js:1 0 DevTools failed to load SourceMap: Could not parse content for file:///C:/Users/chiastinks/AppData/Local/chia-blockchain/app-1.1.4/resources/app.asar/build/renderer/js/80.js.map: Unexpected end of JSON input main.js:1 Already connected, not reconnecting. main.js:1 0 ...

PC101guy commented 3 years ago

Hate this bug, im surprised it hasn't been fixed yet, the thing is the plotter is still running in the background, I can tell by task manager, the only issue is im stuck on connection to wallet and can't get past it, same thing dev shows already connected, not reconnection, then why won't it show my wallet... sucks ill reboot tommorow morning ill just let the plotter run overnight.

intelmib commented 3 years ago

someone managed to solve?

kaygod commented 3 years ago

anyone manage to solve this,thanks

PeterNierop commented 3 years ago

Same here...

pro2pop commented 3 years ago

same trouble

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.

hubertgad commented 3 years ago

up, this bug still exists

zanolera commented 3 years ago

updated to 1.2.0 and this error started here

pictin commented 3 years ago

For me, this was happening during attempted upgrade from 1.1.6 to 1.2.1 on a Windows 7 machine. Chia daemon was failing to start because of an older (3.8) version of python, and failing without writing anything to the log (even at DEBUG level) or presenting anything to gui front-end. After downgrading chia to 1.1.7 problem disappeared. Looks like the root cause (for this particular machine) was Windows 7, and newer versions of chia have fatal incompatibility with it.

Max7e commented 3 years ago

Python 3.9 that being used as part of chia software doesn' support w7. (see https://www.python.org/downloads/release/python-390/)

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.

zanolera commented 3 years ago

So, no pools for people using windows 7 machine? I still in 1.1.7 because of this error.

angryBOT commented 3 years ago

Python 3.9 that being used as part of chia software doesn' support w7. (see https://www.python.org/downloads/release/python-390/)

This is not limited to Windows 7. I have the same issue with Windows 10. I also have Python 3.9 running without issues with other tools.

H34dl3ss commented 3 years ago

Any progress on this one? It's keeping me pinned to 1.1.7...

CodeDeficient commented 3 years ago

For those of you using a Linux based machine, Ubuntu or in my case Lubuntu 20.04, I may have an answer for you. At first I thought it was a port forwarding issue but actually I think it's a connection issue to the debian update servers. I only ran into this after a linux system update. Here's what I did:

  1. Go to Software Sources or Software updates (it was sources for me)
  2. In "Other software" tab unmark all selections.
  3. In "Ubuntu" software tab, find the "Download from" dropbox and select "Main Server" option
  4. Select close
  5. Wait for "reload" prompt and select reload
  6. Retry updating Chia Blockchain again like normal

This worked for me after several different attempts, I hope it works for you.

superhappychris commented 3 years ago

I'm having the same issue on Windows 10. Updated from 1.2.0 to 1.2.5 and it did not fix the problem

UPDATE: Turns out port 55400 was being reserved by Hyper-V (must have happened after a restart). Was able to fix the problem by following the steps outlined in this stack overflow answer. The basic idea is that you need to temporarily disable Hyper-V, reserve the port, and then re-enable Hyper-V.

It would be great if the Chia app could handle the case of port 55400 being unavailable when spinning up the daemon.

RowboTony commented 3 years ago

I just upgraded from 1.2.3 to 1.2.5 and encountered this bug. I uninstalled Chia completely, performed the stack over flow fix, and reinstalled v1.2.5, now it's fixed. But it's very frustrating when a simple version upgrade blows up the whole farm.

emlowe commented 3 years ago

You can change the daemon_port in config.yaml

RowboTony commented 3 years ago

@emlowe yep, I tried that first, and it did not work on any port, that’s when I knew something was very broken, so I proceeded to uninstall/reinstall which fixed it. (Windows 10)

H34dl3ss commented 3 years ago

I just upgraded from 1.2.3 to 1.2.5 and encountered this bug. I uninstalled Chia completely, performed the stack over flow fix, and reinstalled v1.2.5, now it's fixed. But it's very frustrating when a simple version upgrade blows up the whole farm.

Didn't try this myself yet, but to apply the fix mentioned on stackoverflow, Win7 needs a hotfix to have the "excludedportrange" option. See here: https://support.accessdata.com/hc/en-us/articles/204244575-How-can-I-reserve-ports-used-by-PRTK-DNA-so-that-they-are-not-taken-by-other-programs-

jack60612 commented 3 years ago

I just upgraded from 1.2.3 to 1.2.5 and encountered this bug. I uninstalled Chia completely, performed the stack over flow fix, and reinstalled v1.2.5, now it's fixed. But it's very frustrating when a simple version upgrade blows up the whole farm.

Didn't try this myself yet, but to apply the fix mentioned on stackoverflow, Win7 needs a hotfix to have the "excludedportrange" option. See here: https://support.accessdata.com/hc/en-us/articles/204244575-How-can-I-reserve-ports-used-by-PRTK-DNA-so-that-they-are-not-taken-by-other-programs-

Windows 7 has never been and never will be supported.

H34dl3ss commented 3 years ago

Windows 7 has never been and never will be supported.

Understood, but it runs fine until 1.1.7, then this issue kicks in - obviously not directly related to the OS. I suppose later versions will also run on W7.

jack60612 commented 3 years ago

Windows 7 has never been and never will be supported.

Understood, but it runs fine until 1.1.7, then this issue kicks in - obviously not directly related to the OS. I suppose later versions will also run on W7.

we don't care if that's the case as i should have never worked at all as windows 7 is insecure

pictin commented 3 years ago

Windows 7 has never been and never will be supported.

Understood, but it runs fine until 1.1.7, then this issue kicks in - obviously not directly related to the OS. I suppose later versions will also run on W7.

The issue here is Python 3.9. Unless somebody makes Python 3.9 to run on Win 7, Chia (versions after 1.1.7) won't run.

emlowe commented 3 years ago

Closing issue, as this seems either specific to Windows 7, or to Hyper-V reserving ports that Chia uses.