Connecting to wallet..................

[qwerty051]

[lukyrys]

+1

[lukyrys]

Traceback (most recent call last):
  File "chia\daemon\server.py", line 954, in <module>
  File "chia\daemon\server.py", line 950, in main
  File "chia\daemon\server.py", line 944, in run_daemon
  File "asyncio\base_events.py", line 587, in run_until_complete
  File "chia\daemon\server.py", line 936, in async_run_daemon
  File "chia\daemon\server.py", line 144, in start
  File "websockets\server.py", line 965, in __await_impl__
  File "asyncio\base_events.py", line 1389, in create_server
OSError: [Errno 10013] error while attempting to bind on address ('127.0.0.1', 55400): an attempt was made to access a socket in a way forbidden by its access permissions
[9508] Failed to execute script server

My problem solved by stopping vmware / hyperV which reserved ports around 55400

[saschaeggi]

+1 I'm also getting the "Connecting to wallet" screen. Looking in the Console => main.js:1 Already connected, not reconnecting.

[Heivor]

+1 I'm also getting the "Connecting to wallet" screen. Looking in the Console => main.js:1 Already connected, not reconnecting.

Same

[philtreF]

+1

[hhhguany]

Same

[drakunov]

Same, 1.1.2

How to repeat 1) Logged in for 1 st time, started plotting 2) i have opened Keys section 3) Stuck there, because no any back button 4) Pressed Reload in Electron Menu

Connecting to wallet.... .... Plotting is active I have tried different restarts in command line

How to completely restart GUI without stopping plotting?

[ril3y]

I have the same issue.

[philtreF]

I even tried to delete everything from computer including the .chia folder with settings and keys, reinstall the software and the issue persists... Does someone know how to get out of this issue?

[oktaysar16]

Stop Chia (Kill Task)

Delete these folders: C:\Users\yourusername.chia C:\Users\yourusername\AppData\Local\chia-blockchain C:\Users\yourusername\AppData\Roaming\Chia Blockchain

Reinstall Chia. It should now work.

[alexs20]

Stop Chia (Kill Task)

Delete these folders: C:\Users\yourusername.chia C:\Users\yourusername\AppData\Local\chia-blockchain C:\Users\yourusername\AppData\Roaming\Chia Blockchain

Reinstall Chia. It should now work.

It doesn't help

[philtreF]

Yeah I confirm that this doesn't help. Like I wrote before : I even tried to delete everything from computer including the .chia folder with settings and keys. Actually I made a new try, I deleted also some Chia-related registry keys and even that did not help. There is nothing else to do other than waiting until the developers see this issue and somehow look into this...

[oktaysar16]

May work for some and wont work for others. I already posted this work around to Reddit posts with same issue and it has already helped multiple people.

[MrGreenApe]

To see the list of blocked ports in windows use: netsh interface ipv4 show excludedportrange protocol=tcp

If port 55400 is that list of port ranges use: net stop winnat [start chia] net start winnat

[ramcsamal]

To see the list of blocked ports in windows use: netsh interface ipv4 show excludedportrange protocol=tcp

If port 55400 is that list of port ranges use: net stop winnat [start chia] net start winnat

Thanks, it worked.

[DennisYildirim]

when I type that command, it shows the ports below. And 55400 is not blocked at all. And it simply does not solve the problem at all. Still can't sync to chia, still can't use the chia node. But somehow my HPool shows my miner as active, and keeps giving me rewards? Even when chia gui is completely closed.

C:\Users\buzad>netsh interface ipv4 show excludedportrange protocol=tcp

Protocol tcp Port Exclusion Ranges

Start Port End Port

---

  5357        5357
  5426        5426
 49780       49879
 49880       49979
 50000       50059     *
 50060       50159
 50160       50259
 50260       50359
 50510       50609
 50610       50709
 50710       50809
 50810       50909
 50910       51009
 54235       54235
 54236       54236

• • Administered port exclusions.

C:\Users\buzad> C:\Users\buzad>

[github-actions[bot]]

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.

[github-actions[bot]]

This issue was automatically closed because it has been flagged as stale and subsequently passed 7 days with no further activity.