IPFS Node config initialised with `0` for all local address ports
See original GitHub issue- Remove
~/.ipfs
- Start IPFS Desktop
- Confirm “Install IPFS”
- Open IPFS node config
"Addresses": {
"API": "/ip4/127.0.0.1/tcp/0",
"Announce": null,
"Gateway": "/ip4/127.0.0.1/tcp/0",
"NoAnnounce": null,
"Swarm": [
"/ip4/127.0.0.1/tcp/0"
]
},
The ports are all set to 0 which is weird, and it means that I can’t connect to the desktop ipfs api from ipfs-companion
Issue Analytics
- State:
- Created 6 years ago
- Comments:18 (17 by maintainers)
Top Results From Across the Web
IPFS Node config initialised with `0` for all local address ports
@olizilla so I just need to change them to the other "defaults". Should I use these (from go-ipfs defaults)?. Swarm listening on /ip4/10.0.75.1/ ......
Read more >Lesson: Connect your node to the IPFS network
This lesson shows how to connect the IPFS node on your local computer to the IPFS network, or “the swarm”. Everything that you...
Read more >Configure a node - IPFS Docs
IPFS is configured through a json formatted text file, located by default at ~/.ipfs/config . Implementation-specific information can be found within the Kubo ......
Read more >Configure a node - IPFS Docs
Configure a node. IPFS is configured through a json formatted text file, located by default at ~/.ipfs/config .
Read more >Configure profile - IPFS Docs
Your IPFS profile is found within your node's config file. The default location for the config file is ~/.ipfs/config . If you have...
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
@olizilla fyi - I’m working on the flag thingy.
Yes they are. SInce once of the most frequent use cases of ipfsd-ctl is tests and the ability to run several daemons in parallel we defaulted to that.