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.

Sign up for GitHub

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

Jump to bottom

0 connected peers #65

Closed
usrprl3alcp-3epl opened this issue Feb 20, 2021 · 2 comments
Closed

0 connected peers #65

usrprl3alcp-3epl opened this issue Feb 20, 2021 · 2 comments

Comments

@usrprl3alcp-3epl
Copy link

I have tried installing seed node and was seeing 0 connected peers every time.
Upstream was used as a connection tool.
We have noticed in discord chat that checkout back to the previous commit f1462b9 fixes this error.
I'm able to see connected peers, and logs show me that process going successfully.
Please check this commit f8338de it seems contains some bug related to connection with peers.
@FintanH
Copy link
Contributor

FintanH commented Feb 22, 2021

What version of Upstream were you using? It's currently known that f8338de is incompatible until radicle-dev/radicle-upstream#1463 lands -- which should be soon.

@xla
Copy link
Contributor

xla commented Feb 22, 2021

This is a known incompatibility and will be remedied soon, in the meantime #72 will contextualise the current state. Thanks for reporting the problem.

@xla xla closed this as completed Feb 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@xla @FintanH @usrprl3alcp-3epl