Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug (hubble): Issue in Peers #2375

Closed
iiamscarface opened this issue Oct 23, 2024 · 1 comment
Closed

bug (hubble): Issue in Peers #2375

iiamscarface opened this issue Oct 23, 2024 · 1 comment
Labels
s-triage Needs to be reviewed, designed and prioritized

Comments

@iiamscarface
Copy link

Hi Team,

I have bootstrapped the hub with a non-default peer by adding the following line to your .env file: BOOTSTRAP_NODE=/dns/hoyt.farcaster.xyz/tcp/2282

After this 1 peer showed up for like an hour but later it again started showing Zero.

Is that an issue or not?

Please refer screenshot attached.
Farcaster Peer Issue

@github-actions github-actions bot added the s-triage Needs to be reviewed, designed and prioritized label Oct 23, 2024
@sds
Copy link
Member

sds commented Oct 31, 2024

In the middle of your screen you can see that you have no inbound connections. This is a network configuration on your side—other hubs can't communicate with you, you can only communicate with them (via outbound connections).

We highly recommend using a provider like Neynar instead of running your own hub. In general, we won't assist with network configuration issues as they are not in our control.

@sds sds closed this as completed Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
s-triage Needs to be reviewed, designed and prioritized
Projects
None yet
Development

No branches or pull requests

2 participants