#Tunnel uplink

Every proxy already leaves the internet through its own dongle. The tunnel uplink is something else: the link your box itself uses to reach our server (the tunnel that carries all proxy connections, and the box's calls to the panel). By default that is the box's default route — normally Ethernet. If Ethernet, your router or your ISP goes down, the tunnel drops and every proxy of the node goes offline, even though each dongle still has data.

With a backup uplink the box moves the tunnel to one of its dongles instead, and back to Ethernet when it works again. Needs agent 1.7.0 or newer; older agents ignore the setting and keep using the default route ("supported": false). In the panel: Nodes → node → Tunnel uplink. Not available to reseller sub-users (404).

:::warning What it costs

• While the box is on a backup dongle, that SIM carries the traffic of all proxies of the node (about the node's total traffic, both directions). Check its data plan.
• Rotating the uplink dongle (auto-rotate, rotation link, API) changes its IP: the tunnel reconnects within a few seconds and open connections on every proxy of the node drop. warnings.auto_rotate_dongle_ids lists chosen dongles that have auto-rotate on — consider Sticky IP for them.
• Switching uplink drops open proxy connections once; new ones work within seconds. :::

#The uplink object

{"node_id": 12, "mode": "auto", "dongle_ids": [9, 7], "return_after_s": 60, "supported": true,
 "status": {"state": "dongle", "text": "Backup: Jio 1", "active": "dongle", "dongle_id": 9, "iface": "huawei81",
            "since": "2026-10-10T19:02:11Z", "switches": 3,
            "last_error": "default route: dial tcp 152.67.6.160:7443: i/o timeout",
            "reported_at": "2026-10-10T19:05:00+00:00"},
 "dongles": [{"id": 7, "label": "Port 30000", "port": 30000, "auto_rotate": false, "uplink_bytes_in": 0, "uplink_bytes_out": 0},
             {"id": 9, "label": "Jio 1", "port": 30001, "auto_rotate": true, "uplink_bytes_in": 1500000, "uplink_bytes_out": 420000}],
 "warnings": {"auto_rotate_dongle_ids": [9]}}

The node object also carries a short "uplink": {"mode", "state", "text"}.

#Get the uplink

Ability: read

curl 'https://proxykite.com/api/v1/nodes/12/uplink' \
  -H "Authorization: Bearer $HYP_TOKEN" \
  -H 'Accept: application/json'

import os
import requests

r = requests.get(
    "https://proxykite.com/api/v1/nodes/12/uplink",
    headers={"Authorization": f"Bearer {os.environ['HYP_TOKEN']}", "Accept": "application/json"},
    timeout=30,
)
print(r.status_code, r.json())

const res = await fetch('https://proxykite.com/api/v1/nodes/12/uplink', {
  headers: {
    Authorization: `Bearer ${process.env.HYP_TOKEN}`,
    Accept: 'application/json',
  },
  signal: AbortSignal.timeout(30000),
});
console.log(res.status, await res.json());

<?php
$ch = curl_init('https://proxykite.com/api/v1/nodes/12/uplink');
curl_setopt_array($ch, [
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_TIMEOUT => 30,
    CURLOPT_HTTPHEADER => [
        'Authorization: Bearer ' . getenv('HYP_TOKEN'),
        'Accept: application/json',
    ],
]);
$body = curl_exec($ch);
$status = curl_getinfo($ch, CURLINFO_HTTP_CODE);
var_dump($status, json_decode($body, true));

Response 200: {"data": <uplink object>}

#Change the uplink

Ability: manage · Who: owner or team admin. The box picks the change up within one heartbeat (~15 s).

curl -X PUT 'https://proxykite.com/api/v1/nodes/12/uplink' \
  -H "Authorization: Bearer $HYP_TOKEN" \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{"mode":"auto","dongle_ids":[9,7],"return_after_s":60}'

import os
import requests

r = requests.put(
    "https://proxykite.com/api/v1/nodes/12/uplink",
    headers={"Authorization": f"Bearer {os.environ['HYP_TOKEN']}", "Accept": "application/json"},
    json={"mode": "auto", "dongle_ids": [9, 7], "return_after_s": 60},
    timeout=30,
)
print(r.status_code, r.json())

const res = await fetch('https://proxykite.com/api/v1/nodes/12/uplink', {
  method: 'PUT',
  headers: {
    Authorization: `Bearer ${process.env.HYP_TOKEN}`,
    Accept: 'application/json',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({"mode":"auto","dongle_ids":[9,7],"return_after_s":60}),
  signal: AbortSignal.timeout(30000),
});
console.log(res.status, await res.json());

<?php
$ch = curl_init('https://proxykite.com/api/v1/nodes/12/uplink');
curl_setopt_array($ch, [
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_CUSTOMREQUEST => 'PUT',
    CURLOPT_TIMEOUT => 30,
    CURLOPT_HTTPHEADER => [
        'Authorization: Bearer ' . getenv('HYP_TOKEN'),
        'Accept: application/json',
        'Content-Type: application/json',
    ],
    CURLOPT_POSTFIELDS => '{"mode":"auto","dongle_ids":[9,7],"return_after_s":60}',
]);
$body = curl_exec($ch);
$status = curl_getinfo($ch, CURLINFO_HTTP_CODE);
var_dump($status, json_decode($body, true));

Response 200: {"data": <uplink object>}. 422 validation_failed for an unknown mode, more than 3 ids, an id that is not a dongle of this node, return_after_s out of range, or auto/dongle without a dongle.

#Alerts

Under Account → Alerts (or PATCH /alerts/settings, see Alerts) the owner gets, once per change: uplink_backup (the tunnel moved to a dongle), uplink_primary (back on Ethernet) and uplink_none (no link worked for two heartbeats in a row). Times are in your timezone.