Connection error: CRITICAL: Problem with remote registration thread

sebwx commented 1 year ago

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.

Android screenshot 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

mtwebster commented 1 year ago

So to make sure I understand,

You have 3 computers and an android phone.
2 of the computers and the android phone have no issues between themselves.
One of the secondary computers can see the main (from your log file)
Your main computer can't see anything else at all

The registration fails on the secondary computer because there's no response from the main one - it will ignore any registration calls that aren't from 'discovered' devices.

The main computer -

do you have any sort of VPN or other type of ip tunnel active?
You're certain everything is on the same subnet? (192.168.1.*)
It seems like it's probably ok, but double-check in preferences->Connection that the correct network interface is selected, or probably automatic is fine also.

If you use avahi-browse _warpinator._tcp in a terminal from the main computer does that show any of the other devices? (This avahi/zeroconf is how machines on the network are 'discovered').

sebwx commented 1 year ago

Hello @mtwebster, Yes you understood correctly

do you have any sort of VPN or other type of ip tunnel active?

No I don't use VPN, I don't think I have any ip tunnel but I am not an expert. Maybe it is possible that I tweaked something wrong.

You're certain everything is on the same subnet? (192.168.1.*)

Yes my main computer is showing 192.168.1.43 in warpinator and my secondary one 192.168.1.44

It seems like it's probably ok, but double-check in preferences->Connection that the correct network interface is selected, or probably automatic is fine also.

I checked and it is on automatic (I only use wifi on all the computers).

If you use avahi-browse _warpinator._tcp in a terminal from the main computer does that show any of the other devices? (This avahi/zeroconf is how machines on the network are 'discovered').

The main computer (OMEN) only detect himself:

+   wlo1 IPv4 OMEN-6E1BEA566F45B70545A5                     _warpinator._tcp     local
-   wlo1 IPv4 OMEN-6E1BEA566F45B70545A5                     _warpinator._tcp     local
+   wlo1 IPv4 OMEN-6E1BEA566F45B70545A5                     _warpinator._tcp     local

The secondary computer (MSI-TV) detects the main one:

+   wlp2s0 IPv4 OMEN-6E1BEA566F45B70545A5                     _warpinator._tcp     local
+   wlp2s0 IPv4 MSI-TV-95B6DD363ED4784B097D                     _warpinator._tcp     local

I tried to purge warpinator and reinstall it and the problem is still there. I alos booted the computer on live version of Linux Mint and warpinator works perfectly fine then.

Mikael63-me commented 1 year ago

I got almost the same issue. PC1: Linux Mint 21.1 -64 (cinnamon) PC2: LMDE 5 M1: Android S21

PC1-PC2 = OK PC2-M1=OK PC1-M1= Not OK warpinator::DEBUG: >>> Discovery: new remote: Mikaels S21 (192.168.1.84:42000) -- server.py (line 247) warpinator::DEBUG: Registering with Mikaels S21 (192.168.1.84:42001) - api version 2 -- remote_registration.py (line 203) warpinator::DEBUG: remote-registration-thread-Mikaels S21-192.168.1.84:42001-970083bc-c18b-4a84-957f-63700ca79138 -- remote_registration.py (line 208) warpinator::DEBUG: Remote: Attempting to register Mikaels S21 (192.168.1.84) -- remote_registration.py (line 224) warpinator::CRITICAL: Problem with remote registration thread: Mikaels S21 (192.168.1.84:42001) - api version 2: -- remote_registration.py (line 239) warpinator::DEBUG: Unable to register with Mikaels S21 (192.168.1.84:42001) - api version 2 -- remote_registration.py (line 218) warpinator::WARNING: Register failed, or the server was shutting down during registration, ignoring remote Mikaels S21 (192.168.1.84:42000) auth port: 42001 -- server.py (line 260) Edit: Firewall is Off Edit2: Ping PC2->M1=OK, Ping PC1->M1="Destination Host Unreachable"

Mikael63-me commented 1 year ago

Not sure if this is a permanent solution but when I removed, from "Network connection" (PC1), my wireless connection and then connect to the "new" discovered wifi - I got connection PC1-M1 to work again!

Edit: NOT a permanent solution..

linuxmint / warpinator