lbryio / lbryio/lbry-desktop

LBRY network status indicator in App

Open
#7,198 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
3.5k
Forks
409
PR merge metrics
No merged PRs in 30d

Description

## The Issue
As a LBRY user, I want to make sure that my PC and network configuration allows for the sharing and consuming content. We should have some type of indicator which checks connectivity on the daemon TCP port (3333) and the DHT UDT port (4444).

For content sharing to properly work, hosts need port 3333 accessible and open to the internet. If the port is not forwarded correctly, their PC won't be able to host but it may still be able to reach out to the reflector servers. If something is blocking port 3333, it won't be able to reach out to the reflector servers, so the content won't be available at all.

For content consumption to work, LBRY needs to be able to connect to the DHT network to find peers. If something is blocking the port, the user experience is really poor - all downloads/streams will hang. There is no indication that something is wrong or needs to be changed.

Probably need an easier way to set these ports, or have LBRY try other ports to see what works.

Background: I've run into a couple users whose ISP blocks port 4444 and they were not able to stream until the port was changed to something else. We also have users who run mining software on port 3333, so if this is taken up by the network, they won't have a proper daemon connection.

## System Configuration

- LBRY Daemon version:
- LBRY App version:
- LBRY Installation ID:
- Operating system:

## Anything Else

## Screenshots

### Acceptance Criteria
1.
2.
3.

### Definition of Done
- [ ] Tested against acceptance criteria
- [ ] Tested against the assumptions of the user story
- [ ] The project builds without errors
- [ ] Unit tests are written and passing
- [ ] Tests on devices/browsers listed in the issue have passed
- [ ] QA performed & issues resolved
- [ ] Refactoring completed
- [ ] Any configuration or build changes documented
- [ ] Documentation updated
- [ ] Peer Code Review performed

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No implementation files or tests are identified in the issue. Start with the app's Help/About area and investigate how the daemon TCP port 3333 and DHT UDT port 4444 are configured and reached; done requires agreed acceptance criteria for reporting connectivity and handling blocked or conflicting ports.

Written by the indexing model from the issue text.

Assessment

Tech stack
electron, javascript
Domain
frontend, networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.