[BUG] Won't start without ipv6 stack with default config
See original GitHub issueDescribe the bug
trying to run chia-blockchain
without an ipv6 stack doesn’t work
I did not find a way to override the bound address in the config
EDIT: config workaround that works for me
/usr/share/chia-blockchain/app.asar.unpacked/daemon
true
Error loading config - using defaults
startUrl file:///usr/share/chia-blockchain/app.asar/build/renderer/index.html
/usr/share/chia-blockchain/app.asar.unpacked/daemon
true
/usr/share/chia-blockchain/app.asar.unpacked/daemon
true
Running python executable:
child process success
(node:16229) electron: The default of contextIsolation is deprecated and will be changing from false to true in a future release of Electron. See https://github.com/electron/electron/issues/23506 for more information
No cert
Have cert
stderr: 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 616, in run_until_complete
File "chia/daemon/server.py", line 936, in async_run_daemon
File "chia/daemon/server.py", line 137, in start
File "websockets/server.py", line 965, in __await_impl__
File "asyncio/base_events.py", line 1463, in create_server
OSError: [Errno 99] error while attempting to bind on address ('::1', 55400, 0, 0): cannot assign requested address
[16275] Failed to execute script server
closing code: 255
nothing is using the port as shown by:
❯ sudo ss -tulpn | grep :55400
To Reproduce Steps to reproduce the behavior:
- Disable ipv6 (https://wiki.archlinux.org/index.php/IPv6#Disable_IPv6)
- Run
chia-blockchain
Expected behavior Work, or at least allow to specify an ipv4 address to bind to
Screenshots
Desktop (please complete the following information):
- OS: Linux
- OS Version/Flavor: 5.11.13-arch1-1/Arch
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Bug #1878682 “IPv6 not enabled by default” : Bugs : cloud-init ...
I can enable IPv6 using "network-config" on a NoCloud cidata volume, ... This bug should probably be "cloud-init does not wait for IPv6...
Read more >Cannot configure ipv6 on 2960 - Cisco Community
I'm new to cisco command language, so please be gentle. lol As part of a class, in Packet Tracer, I have to configure...
Read more >1362528 – Unable to disable IPv6 RAs acceptance on ...
Cause: Due to logic in the kernel, net.ipv6.conf.default.autoconf and accept_ra are not by themselves sufficient to disable those features ...
Read more >Configure IPv6 for advanced users - Windows Server
Use registry key to configure IPv6 ; Disable IPv6 on all nontunnel interfaces (except the loopback) and on IPv6 tunnel interface, Decimal 17...
Read more >How to disable IPv6 permanently? - Ask Ubuntu
If your PC doesn't load /etc/sysctl.conf at boot time (which is the case for me), disabling IPv6 from grub is needed. Linux kernel...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This seems to be a known issue in some way. The
chia-docker
repository shows the workaround: https://github.com/Chia-Network/chia-docker/blob/main/entrypoint.shLine 20:
Replacing all references to
localhost
with it’s IPv4 loopback address127.0.0.1
inconfig.yml
prevents it from being resolved to IPv6::1
.This fixed the issue for me.
One question remains though: is it a bug or is it a feature?
This issue was automatically closed because it has been flagged as stale and subsequently passed 7 days with no further activity.