Connection troubleshooting

Registration, the management connection and model serving are separate checks.

AVENTAIL / PROCESS GUIDE

Locate the failure

At a glance

Locate the failure

Start with the device and exact error. Keep network protections enabled while diagnosing.

Process overview

1. 1
   Local serviceCheck the installed version and service status
2. 2
   Management connectionCheck account and outbound connectivity
3. 3
   Model endpointTest serving separately

Step 1 of 1: Locate the failure.

Process overview; detailed actions and examples are below.

AVENTAIL / PROCESS GUIDE

Locate the failure

At a glance

Locate the failure

Start with the device and exact error. Keep network protections enabled while diagnosing.

Process overview

1. 1
   Local serviceCheck the installed version and service status
2. 2
   Management connectionCheck account and outbound connectivity
3. 3
   Model endpointTest serving separately

Step 1 of 1: Locate the failure.

Read the network checks and commands

A registration success message does not prove that Link's background connection is ready.

Check the device first

For Aventail Link 2.x, run:

aventail status

If the desktop executable is not on your PATH, use its full installation path.

If it needs starting or restarting, follow Restart Link. For Locai Link (Legacy Aventail) 1.x, use locai status and locai start instead.

Confirm the account and device in Control. Record the exact error before retrying registration or reinstalling.

Test connectivity

Use the destination named in the error. The production Locai Link (Legacy Aventail) 1.3.2 walkthrough used tls/zenoh.locai.co.uk:7448; a build configured for another environment can use different hosts.

macOS / Linux:

nc -zv zenoh.locai.co.uk 7448

Windows PowerShell:

Test-NetConnection -ComputerName zenoh.locai.co.uk -Port 7448

Success confirms a TCP connection, not a successful TLS session or account authentication. Failure may involve DNS, routing, a firewall or the remote service; it does not identify the cause by itself.

Network requirements

Purpose	Destination	Port
Registration and management API	api.locai.co.uk	TCP 443 / HTTPS
Device messaging	zenoh.locai.co.uk	TCP 7448 / TLS
Installer and release downloads	get.aventail.co.uk; get.locai.co.uk for compatibility with 2.0.0 metadata	TCP 443 / HTTPS
Release artifacts referenced by metadata	storage.googleapis.com	TCP 443 / HTTPS

Development and staging use their corresponding dev. and staging. release hosts and different management endpoints. Use the command generated by that environment. Historical 1.x packages use GitHub and its download redirects.

Model and engine downloads may use additional artifact hosts. Ask your administrator to review the actual destination in a failed-download log rather than treating this as a complete allowlist.

On a managed network, ask the administrator to check the failed connection and certificate trust. Keep network protections enabled. After resolving access, restart Link and confirm Online.

For local model access, see serving endpoints. Outbound Control connectivity and inbound access to a model's port are different requirements.