Running hyp seed hyper://<bee address> results in a message that says Seeding <bee address>, but running hyp info after that still results in the bee "Not seeding and not online" and others are unable to seed or access the bee.
Alternatively, if I run a Node server locally that serves a hyperbee (built using this tutorial from Paul Frazee) others are able to seed/access that same bee. After running a hyp info here while the server is running, the CLI says "Not seeding but online (announcing)". But again, they can actually seed and access the bee.
Since the bee is able to be accessed when the Node server is running, but not when trying to seed it manually from the CLI, I'm assuming there's an issue with the CLI and seeding bees. I am new to Hypercore in general, so perhaps it's user error, but I thought I'd surface this in case it's not.
Running
hyp seed hyper://<bee address>results in a message that saysSeeding <bee address>, but runninghyp infoafter that still results in the bee "Not seeding and not online" and others are unable to seed or access the bee.Alternatively, if I run a Node server locally that serves a hyperbee (built using this tutorial from Paul Frazee) others are able to seed/access that same bee. After running a
hyp infohere while the server is running, the CLI says "Not seeding but online (announcing)". But again, they can actually seed and access the bee.Since the bee is able to be accessed when the Node server is running, but not when trying to seed it manually from the CLI, I'm assuming there's an issue with the CLI and seeding bees. I am new to Hypercore in general, so perhaps it's user error, but I thought I'd surface this in case it's not.