Open rebelxt opened 1 month ago
Should not be an issue, these are both recent versions.
There's a lot of troubleshooting info in the README, and running with --debug
may help yield some clues also.
I believe all considerations in README are satisfied. Two Linux Mint machines on the network connect, and as best I can tell, NixOS is set up similarly. Since much of NixOS is defined in a configuration file, it can be difficult to be absolutely sure. I am attaching --debug info from both machines. Nothing correctable jumps out at me. warp-debug-Nix.txt warp-debug-LM.txt
Do you have another machine sharing an ip address?
2024-10-14 14:45:38,606::warpinator::DEBUG: Using selector: EpollSelector -- selector_events.py (line 54)
2024-10-14 14:45:45,773::warpinator::DEBUG: Registration Server RPC: RequestCertificate from MM22 '192.168.1.113' -- remote_registration.py (line 271)
2024-10-14 14:45:45,779::warpinator::DEBUG: Registration Server RPC: RequestCertificate from Asus-K55A '192.168.1.113' -- remote_registration.py (line 271)
2024-10-14 14:45:45,983::warpinator::DEBUG: Server RPC: WaitingForDuplex from 'MM22' (api v2) -- server.py (line 429)
No.
Lines 29 and 56 in warp-debug-LM.txt show the IP addresses of the remote (to LM) machines.
The IP addresses in lines 21 and 22 in warp-debug-Nix.txt are not the remote (to Nix) machines, but it's own IP address.
Distribution
Mint 22 Mate and NixOS 24.11
Package version
1.8.6 and 1.6.4
Frequency
Always
Bug description
Mint recognizes the NixOS machine, but NixOS cannot connect to the Mint machine. Before I go any deeper into this process, will the different versions of Warpinator prevent a connection from being made?
Steps to reproduce
N/A
Expected behavior
N/A
Additional information
I have debug information which I will supply if the version difference should not be a problem.