NVIDIA / NVIDIA/Personal-AI-Router
[Bug]: Offline node after successful pairing over VPN connection
@ckelseynv ya está trabajando en esto.
Desde el 18/9/2026.
- Lenguaje dominante
- Go
- Estrellas
- 1.4k
- Forks
- 250
- Merge medio
- 23 h 27 min
- PR fusionados (30 d)
- 1
Descripción
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
Steps to reproduce
- Install ollama on both computers and pull some modells.
- Install PAIR desktop on both computers, Apple M4 Max, macOS.
- Setup VPN connection between the computers (I am using Wireguard).
- Turn off the firewall on both computers.
- 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.
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Evaluación
Este issue todavía no se ha evaluado.