From 4f558ed57675a5c0fe4817bb15b50ae05460d0d9 Mon Sep 17 00:00:00 2001
From: Will Anderson <will@neuralplatform.ai>
Date: Wed, 15 Apr 2026 02:48:47 -0500
Subject: [PATCH] Fix ProtonVPN server names to match registered WireGuard keys

Keys in Vault are registered for US-TX#253 (tx253 worker) and US-TX#34
(tx34 worker), but deployment was connecting to US-TX#179 and US-TX#220.
WireGuard handshake succeeded globally but ProtonVPN only routes internet
traffic through the server the key was registered with.
---
 servers/legion/k8s/media/fornax-workers.yaml | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/servers/legion/k8s/media/fornax-workers.yaml b/servers/legion/k8s/media/fornax-workers.yaml
index 648a713..18659e2 100644
--- a/servers/legion/k8s/media/fornax-workers.yaml
+++ b/servers/legion/k8s/media/fornax-workers.yaml
@@ -1,10 +1,10 @@
 # Fornax distributed torrent workers — each is a gluetun+qBittorrent pod on a different VPN server
-# Worker TX#179: US-TX#179, NAT-PMP via gluetun native ProtonVPN port forwarding
-# Worker TX#220: US-TX#220, NAT-PMP via gluetun native ProtonVPN port forwarding
+# Worker tx253: US-TX#253 (endpoint 95.173.217.29), WireGuard key in vault secret/fornax/worker-tx253
+# Worker tx34: US-TX#34 (endpoint 146.70.58.130), WireGuard key in vault secret/fornax/worker-tx34
 # Both workers share the media-data PVC; each has its own config PVC and VPN credentials
 # Port file shared via emptyDir: gluetun writes /tmp/gluetun/forwarded_port, helper reads it
 
-# ── Worker TX#179 ─────────────────────────────────────────────────────────────
+# ── Worker TX#253 ─────────────────────────────────────────────────────────────
 apiVersion: apps/v1
 kind: Deployment
 metadata:
@@ -13,7 +13,7 @@ metadata:
   labels:
     app: fornax-worker-tx253
     fornax-role: worker
-    fornax-server: us-tx-179
+    fornax-server: us-tx-253
 spec:
   replicas: 1
   strategy:
@@ -26,7 +26,7 @@ spec:
       labels:
         app: fornax-worker-tx253
         fornax-role: worker
-        fornax-server: us-tx-179
+        fornax-server: us-tx-253
     spec:
       initContainers:
         - name: tun-setup
@@ -101,7 +101,7 @@ spec:
                   name: fornax-worker-tx253-secrets
                   key: PROTONVPN_PRIVATE_KEY
             - name: SERVER_NAMES
-              value: "US-TX#179"
+              value: "US-TX#253"
             - name: VPN_PORT_FORWARDING
               value: "on"
             - name: DOT
@@ -254,7 +254,7 @@ spec:
   type: ClusterIP
 
 ---
-# ── Worker TX#220 ─────────────────────────────────────────────────────────────
+# ── Worker TX#34 ──────────────────────────────────────────────────────────────
 apiVersion: apps/v1
 kind: Deployment
 metadata:
@@ -263,7 +263,7 @@ metadata:
   labels:
     app: fornax-worker-tx34
     fornax-role: worker
-    fornax-server: us-tx-220
+    fornax-server: us-tx-34
 spec:
   replicas: 1
   strategy:
@@ -276,7 +276,7 @@ spec:
       labels:
         app: fornax-worker-tx34
         fornax-role: worker
-        fornax-server: us-tx-220
+        fornax-server: us-tx-34
     spec:
       initContainers:
         - name: tun-setup
@@ -351,7 +351,7 @@ spec:
                   name: fornax-worker-tx34-secrets
                   key: PROTONVPN_PRIVATE_KEY
             - name: SERVER_NAMES
-              value: "US-TX#220"
+              value: "US-TX#34"
             - name: VPN_PORT_FORWARDING
               value: "on"
             - name: DOT