OSError: [Errno 99] error while attempting to bind on address ('::1', 55400, 0, 0): cannot assign requested address
See original GitHub issue[ERR] chia start timelord
Check list
- chia init✅
- chia keys generate✅
- chia plots create -k 32 -n 2✅
- chia start timelord🚫
Error
OSError: [Errno 99] error while attempting to bind on address ('::1', 55400, 0, 0): cannot assign requested address
Daemon not started yet
Failed to create the chia daemon
Logs
Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-70-generic x86_64)
(venv) root@vmi777:~/chia-blockchain# chia start timelord
Daemon not started yet
Starting daemon
Traceback (most recent call last):
File "/root/chia-blockchain/venv/bin/chia", line 33, in <module>
sys.exit(load_entry_point('chia-blockchain', 'console_scripts', 'chia')())
File "/root/chia-blockchain/src/cmds/chia.py", line 77, in main
cli() # pylint: disable=no-value-for-parameter
File "/root/chia-blockchain/venv/lib/python3.8/site-packages/click/core.py", line 829, in __call__
return self.main(*args, **kwargs)
File "/root/chia-blockchain/venv/lib/python3.8/site-packages/click/core.py", line 782, in main
rv = self.invoke(ctx)
File "/root/chia-blockchain/venv/lib/python3.8/site-packages/click/core.py", line 1259, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/root/chia-blockchain/venv/lib/python3.8/site-packages/click/core.py", line 1066, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/root/chia-blockchain/venv/lib/python3.8/site-packages/click/core.py", line 610, in invoke
return callback(*args, **kwargs)
File "/root/chia-blockchain/venv/lib/python3.8/site-packages/click/decorators.py", line 21, in new_func
return f(get_current_context(), *args, **kwargs)
File "/root/chia-blockchain/src/cmds/chia.py", line 60, in run_daemon_cmd
asyncio.get_event_loop().run_until_complete(async_run_daemon(ctx.obj["root_path"]))
File "/usr/lib/python3.8/asyncio/base_events.py", line 616, in run_until_complete
return future.result()
File "/root/chia-blockchain/src/daemon/server.py", line 932, in async_run_daemon
await ws_server.start()
File "/root/chia-blockchain/src/daemon/server.py", line 137, in start
self.websocket_server = await serve(
File "/root/chia-blockchain/venv/lib/python3.8/site-packages/websockets/server.py", line 965, in __await_impl__
server = await self._create_server()
File "/usr/lib/python3.8/asyncio/base_events.py", line 1463, in create_server
raise OSError(err.errno, 'error while attempting '
OSError: [Errno 99] error while attempting to bind on address ('::1', 55400, 0, 0): cannot assign requested address
Daemon not started yet
Failed to create the chia daemon
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
OSError: [Errno 99] error while attempting to bind on address ...
For VPC network type ECS instances, the public IP of the ECS instance is not visible inside the OS, hence you cannot bind...
Read more >Error while attempting to bind address? : r/chia - Reddit
... None OSError: [Errno 99] error while attempting to bind on address ('::1', 55400, 0, 0): cannot assign requested address closing code: 1....
Read more >How I fixed Python OSError: [Errno 99] Cannot assign ...
In my case, the issue was that I was trying to bind the specific IP address 192.168.1.100 but the computer running the script...
Read more >OSError: [Errno 99] Cannot assign requested address - Medium
This error is seen when tornado tries to bind IP/port when Jupyter Enterprise Gateway starts. jupyter-enterprisegateway --ip=hostname.domain.com.
Read more >The small linux problem thread - #4135 by anon86748826
OSError: [Errno 99] error while attempting to bind on address ('::1', 55400, 0, 0):. ::1 is an ipv6 local host address. try setting...
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
Figured it out. So, the default generated
config.yaml
definesself_hostname
asself_hostname: &self_hostname "localhost"
.If you don’t have IPv6 enabled in your environment, requests will still resolve
localhost
to mean::1
and not127.0.0.1
. Replacinglocalhost
with127.0.0.1
allows the node to start successfully.I presume this would work fine on an environment with ipv6 enabled.
Thx! It worked for me.