BUG: '✖ Fetch failed' while creating composites on local ceramic node.

[daniel0ar]

Describe the bug
Ceramic local node starts at http://0.0.0.0:7007, thus all the documentation with http://localhost:7007 doesn't function correctly.

To Reproduce
Steps to reproduce the behavior:

1. Follow steps in https://developers.ceramic.network/docs/composedb/set-up-your-environment#2c-installation-using-javascript-package-managers
2. Follow all steps into until you reach the command:

composedb composite:from-model kjzl6hvfrbw6c5ajfmes842lu09vjxu5956e3xq0xk12gp2jcf9s90cagt2god9 --ceramic-url=http://localhost:7007 --output=my-first-composite.json

3. See error: ✖ fetch failed

Expected behavior
The Ceramic Node should start at localhost:7007 or else all the documentation should switch to http://0.0.0.0:7007 as the --ceramic-url or the -c flag

Machine, OS, browser information (please complete the following information):
Linux, PopOs 22.04, Firefox. Node 20.11.1, npm 10.2.4

[dav1do]

Thanks for taking the time to submit issues and help improve the ceramic DX!

Regarding 0.0.0.0, see this comment for some context. Typically, this is a node version issue, but I see you have node 20 installed (thanks for including your setup, PopOS is the only thing that jumps out at me as a bit unusual/potentially untested by the team, but I've tested on ubuntu). Is it possible the server wasn't running successfully here but when you had it running, it did work on localhost? It seems like you could interact with the server in #79.

How did you get ceramic running in the end? It seems like you had some trouble with the install generally. Your attempts to use wheel (#77) and npx/pnpx (#76) ran into issues. Regarding the wheel install, that looks like it might be the same root issue as the npx install problem, as we rely on npm to install the cli for us to invoke it. The error could certainly be improved if that's the case.

We've released some major updates to js-ceramic and composedb and should verify that isn't causing issues getting started.

[daniel0ar]

Regarding 0.0.0.0. I used manual pnpx install (method 2c. Installation using JavaScript package managers) and I guess it installs ceramic and doesn't add the host and port to the daemon config,
like this:

"hostname": "127.0.0.1",
"port": 7007,

, thus allowing the ceramic node to auto start on 0.0.0.0 instead of localhost. In my case if I don't specify those in any config file it uses 0.0.0.0 as deafult hostname.

[daniel0ar]

As for getting it working, once having the ceramic node running (installed with pnpx), i added localhost hostname and went with the wheel install without ceramic.