Platform
ScaiWave ScaiGrid ScaiCore ScaiBot ScaiDrive ScaiKey Modellen Tools & Services
Oplossingen
Organisaties Ontwikkelaars Internet Service Providers Managed Service Providers AI-in-a-Box
Kenniscentrum
Ondersteuning Documentation Blog Downloads
Bedrijf
Over ons Onderzoek Vacatures Investeren Contact
Inloggen

Connect a network

Quickstart gets one connector running. This page covers doing it properly.

Egress requirements#

The connector needs outbound access only:

Destination Port Purpose
*.edge.proxility.scailabs.ai UDP/443 Data plane. Preferred
*.edge.proxility.scailabs.ai TCP/443 Data plane fallback where UDP is blocked
api.proxility.scailabs.ai TCP/443 Enrolment and certificate renewal

No inbound rules. If your egress filter is name-based, allow the two names above; if it is address-based, proxility edge ranges prints the current prefixes, and they are also published for automated allow-lists.

UDP is strongly preferred — the TCP fallback puts a reliable transport under a reliable transport, and under loss the two congestion controllers interact badly. If you are on the fallback, you will see it in proxility connector list and should fix the filter rather than live with it.

Run two connectors#

A production network gets two connectors on separate hosts, ideally in separate failure domains:

bash
1
2
proxility connector create dc1-a --description "Amsterdam DC, rack 4"
proxility connector create dc1-b --description "Amsterdam DC, rack 11"

Publish each service through both:

bash
1
2
3
4
proxility service create payments \
  --connector dc1-a,dc1-b \
  --target 10.20.4.17:8443 \
  --protocol tcp

Sessions distribute across available connectors. Losing one drops its in-flight connections — clients reconnect and land on the survivor. There is no state to fail over, because there is no shared session state.

Installation#

Platform Method
Debian/Ubuntu apt install proxility-connector from the ScaiLabs repo
RHEL/Rocky dnf install proxility-connector
Container scailabs/proxility-connector:<version>, NET_ADMIN not required
Kubernetes Helm chart scailabs/proxility-connector, one DaemonSet or Deployment per cluster
Windows MSI from /downloads

Builds are published on the ScaiLabs downloads page under Standalone apps & clients.

Upgrades#

Upgrade one connector of a pair at a time:

bash
1
2
3
apt install --only-upgrade proxility-connector
systemctl restart proxility-connector
proxility connector list          # wait for 'connected' before the next one

A connector restart drops its established sessions. With a redundant pair and clients that reconnect, this is invisible; with a single connector it is a brief outage, so schedule it.

Retiring a connector#

bash
1
proxility connector revoke dc1-a

Revocation takes effect at the next handshake — the identity stops being trusted immediately rather than when its certificate expires. Remove the connector from any services it publishes first, or those services lose an endpoint.

Monitoring#

Expose the connector's metrics endpoint to your own scrape target and alert on:

Signal Why
Certificate renewal failure The connector will stop working within 24 hours
Edge sessions below two You are one failure from an outage
Transport = TCP fallback UDP is being blocked somewhere
Policy-deny rate rising Either a misconfiguration or someone probing

Forward the same events to ScaiLog and let ScaiSentry alert on them if you do not want to run your own pipeline.

Updated 2026-11-08 18:08:05 View source (.md) rev 2