Handshake failed
1 2 3 | |
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:
1 2 3 4 | |
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:
1 2 | |
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:
1 | |
Certificate expired#
1 2 | |
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:
1 | |
Then check the ScaiLabs status page and raise it with support, with the output
of proxility-connector status and the region name.