Troubleshooting

Browser certificate warning on the office network

Cause: Office-network HTTPS uses the box CA, which browsers do not trust until you install it.

Fix: Download the box CA from Network or Security, install it for your organisation, reload. Or temporarily proceed for this host only while setting up.

Cannot open locai-….local

• Confirm your laptop is on the same office network as the appliance, not guest Wi‑Fi, a mobile hotspot, or a VPN.
• Try the LAN IP shown on the kiosk over HTTPS if mDNS fails (common across VLANs).
• Confirm the appliance is powered and healthy (Dashboard, the support package on Support, or the kiosk status pulse).

Direct DNS: Check DNS fails

• Confirm the A record points at the public IP shown in Network (not a private office IP).
• Wait for DNS TTL / propagation, then Check DNS again.
• Confirm the appliance can detect a public IP (Refresh). NAT setups may need a correct external mapping for HTTPS.

Public hostname works for some networks but not others

Some enterprise or research networks filter by hostname reputation or category. That is outside the appliance. Use an allowed company domain, or ask that network’s operators to allow your hostname. Office-network access is unaffected.

Model will not load / stays installing

• Check Models for VRAM fit and error detail.
• Confirm disk space under Storage.
• Download a support package from Support if the state does not progress.

Inference or the API returns errors

• Confirm at least one model is healthy on Models.
• Confirm clients use the URL and API base shown under API keys.
• Confirm the API key is active under API keys.
• Try Playground with your admin session to separate key issues from model issues.

Still stuck

1. Note serial, version, and URL from General → About (use Copy for support).
2. Download a diagnostics bundle.
3. Open a time-bounded session under Support if Locai is assisting. Do that in the console, not by pasting session secrets into email.