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

Handshake failed

bash
1
2
3
$ proxility-connector status
identity   prox://acme/prod/dc1-a
edge       0 sessions  (last error: handshake timeout)

A connector with zero edge sessions is invisible to the fabric, and anything it publishes denies with connector_offline.

Is it egress#

Nine times out of ten. The connector needs outbound UDP/443 to *.edge.proxility.scailabs.ai:

bash
1
2
3
4
proxility-connector test --edge-only
# resolve   ok   edge1.nlwest-std.edge.proxility.scailabs.ai
# udp/443   FAIL timeout after 5s
# tcp/443   ok   fallback available

UDP blocked but TCP working means you are on the fallback — it works, and it works worse. Get UDP opened rather than accepting it: reliable transport stacked on reliable transport behaves badly under loss.

MTU#

A handshake that completes and then stalls on the first large transfer is almost always MTU. The data plane adds overhead, and a path that silently drops fragments will pass small packets and lose big ones:

bash
1
2
proxility-connector status | grep mtu
ping -M do -s 1400 edge1.nlwest-std.edge.proxility.scailabs.ai

Lower the connector's MTU until the path stops dropping, and fix the path if you can — a network that drops ICMP fragmentation-needed is broken in ways that will bite other things too.

Clock#

Certificate validation fails on a skewed clock, and the error surfaces as a handshake failure rather than something clearer:

bash
1
timedatectl status

Certificate expired#

bash
1
2
proxility-connector status       # 'certificate expired 3h ago'
proxility-connector renew

If renewal fails with identity_revoked, the identity was revoked deliberately — find out why before re-enrolling.

Edge-side problem#

If egress, MTU and clock all check out and multiple connectors in the same region fail at once, suspect the edge rather than your network:

bash
1
proxility edge status

Then check the ScaiLabs status page and raise it with support, with the output of proxility-connector status and the region name.

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