NVIDIA / NVIDIA/Personal-AI-Router

[Bug]: Offline node after successful pairing over VPN connection

Offen
#65 1 Kommentar 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@ckelseynv arbeitet bereits daran.

Seit 18.9.2026.

bug
Vorherrschende Sprache
Go
Sterne
1.4k
Forks
250
Ø Merge
23 Std. 27 Min.
Gemergte PRs (30 T.)
1

Beschreibung

PAIR version or commit

0.1.1.463

Affected component

Desktop application

Environment

OS: macOS 15.7.8
architecture: arm
GPU: M4 Max
driver: N/A (Apple Silicon / Metal)
engine/version: ollama version is 0.33.3
model: qwen3.8:27b-mlx
cluster size: 2

I have installed PAIR desktop on both computers, Apple M4 Max, macOS.
On both computers I already had ollama up and running.
PAIR discovered the ollama on both computers.
Computers are connected through VPN (Wireguard).
I successfully paired the computers.
The nodes show offline on both computers.

% netstat -an | grep 11435                      
tcp46      0      0  *.11435                *.*                    LISTEN 

% netstat -an | grep 14321
tcp4       0      0  10.0.0.2.51278         10.0.0.12.14321        ESTABLISHED
tcp4       0      0  10.0.0.2.14321         10.0.0.12.49602        ESTABLISHED
tcp46      0      0  *.14321                *.*                    LISTEN
Image
Steps to reproduce
  1. Install ollama on both computers and pull some modells.
  2. Install PAIR desktop on both computers, Apple M4 Max, macOS.
  3. Setup VPN connection between the computers (I am using Wireguard).
  4. Turn off the firewall on both computers.
  5. Pair the 2 instances of PAIR from desktop app

The nodes show offline on both computers.

Expected behavior

The nodes should show online.

Actual behavior

The nodes show offline.

Sanitized logs or screenshots
% netstat -an | grep 11435                      
tcp46      0      0  *.11435                *.*                    LISTEN 

% netstat -an | grep 14321
tcp4       0      0  10.0.0.2.51278         10.0.0.12.14321        ESTABLISHED
tcp4       0      0  10.0.0.2.14321         10.0.0.12.49602        ESTABLISHED
tcp46      0      0  *.14321                *.*                    LISTEN
Confirmations
  • I searched existing issues for duplicates.
  • This is not a security vulnerability.
  • I agree to follow the Code of Conduct.

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.