linuxmint / linuxmint/warpinator
Connection error: CRITICAL: Problem with remote registration thread
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.6k
- Forks
- 115
- PR merge metrics
- No merged PRs in 30d
Description
Distribution
Mint 21.2
Package version
1.6.4
Frequency
Always
Bug description
Hello everyone,
I cannot connect nor detect other Wrapinator on the local network from my main computer.
I installed Warpinator on 2 secondary computer (running with linux mint also) and on my android phone and they all work fine together.
When I run Warpinator as debug mode on one of the secondary computer i see that it can detect my main computer but fail to connect, I get CRITICAL: Problem with remote registration thread (see full report attached).
I installed Warpinator on my Android phone and it can detect warpinator as null@omen but cannot connect to it (see screenshot).
I try to disable the firewall on my main computer and the problem still remain.
Debug terminal from main computer.txt
Debug terminal from secondary computer.txt
Steps to reproduce
Start warpinator on secondary computer
Start warpinator on main computer
Min computer is not detected on the secondary computer
Expected behavior
Connection should be established between computers
Additional information
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the attached “Debug terminal from main computer.txt” and “Debug terminal from secondary computer.txt” reports, then reproduce the failure with Warpinator in debug mode using the listed steps. Trace the remote registration failure and verify that the main computer is detected and can establish a connection from the secondary computer and Android phone.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100