keep getting "the daemon is not active" even after running hyp daemon start

[resession]

restarted computer, reinstalled hypercore-cli but i still keep getting "the daemon is not active", any ideas to fix this?

[metanomial]

Encountering the same issue on two machines. Debian Buster and Windows 10 both running Node.js 16.9.1. I am not encountering this on a third Debian Buster instance running Node 16.9.1, where the daemon starts and is seeding.

PS C:\Users\metanomial> hyp daemon start
Hyperspace daemon started
Mirroring daemon started
Daemon is running.
PS C:\Users\metanomial> hyp daemon status
Daemon not active

[cablehead]

I'm seeing this as well on macOS 11.5.2, node 16.9.1. A workaround for me was to install hyperspace directly npm i hyperspace -g and run the daemon directly in the foreground using $ hyperspace

Actually, that fixed hyp daemon status but other commands, hyp info, hyp create drive, still report The daemon is not active.

[Octalbyte]

I am having this same issue. I can't create hyperdrives.

[Octalbyte]

I guess this has something to do with the address not being hole-punchable? First terminal: Second one: When I tried to hyp create drive, hyp daemon start or hyp daemon status first terminal would log: Remote client opened Remote client closed

[ralphtheninja]

I also had this problem, but downgraded node to v14 and then it worked. Unsure if that was related, but that was something that changed that made it work. Could be worth trying out at least.

[felixdrp]

I am having this same issue. I can't create hyperdrives.

$ hyp daemon start
Hyperspace daemon started
Mirroring daemon started
Daemon is running.
$ hyp daemon status
Daemon not active
$ node -v 
v17.2.0

[ralphtheninja]

It would be nice if some of you could try downgrading node to version 14 and see if that helps you.

[specious]

I cloned the git repo to troubleshoot this issue.

It prints The daemon is not active when running anything other than hyp daemon or hyp beam because hyper.setup() fails:

https://github.com/hypercore-protocol/cli/blob/cd56bb6074b03733aece8b6a8716b8dd90f8ee4d/bin/hyp.js#L104-L114

Which fails because it fails to connect to either hyperspace or the mirroring service:

https://github.com/hypercore-protocol/cli/blob/cd56bb6074b03733aece8b6a8716b8dd90f8ee4d/lib/hyper/index.js#L15-L18

So far, I got it working by simply:

$ npm i -g hyperspace hyperspace-mirroring-service
$ hyperspace
$ hyperspace-mirroring-service

Now it works:

$ hyp info --live
No hypers active.

[alexindigo]

Same here, node v16.13.1, macos 12.1. It should be "auto-connecting", right?

Also BeakerBrowser couldn't connect to hyper:// addresses either, not sure if it's related or not.

[specious]

Check out PR #57 and see if it works.

[robindiddams]

was on node 17, downgraded to 14 and it worked

[ghost]

Check out PR #57 and see if it works.

worked for me :+1:

[dwehrmann]

Linux with node v16.13.2 does not work, either. Same behaviour.

[marvinpoo]

Downgraded to Nodejs v14 after all these comments. Still getting the same response.

$ hyp daemon start
Hyperspace daemon started
Mirroring daemon started
Daemon is running.
$ hyp info --live
The daemon is not active. Please run:

  hyp daemon start

[specious]

If someone could look at PR #57 that would be very helpful.

@pfrazee, could you take a moment?

[pfrazee]

@specious I'm sorry, I really can't -- I'm engaged with a new job rn, I have to punt this to the hypercore team

[marvinpoo]

If someone could look at PR #57 that would be very helpful.

@pfrazee, could you take a moment?

This hotfix seems to solve the problem. Thank you!

[luandro]

Solves it :tada: