Skip to main content
Most issues have a quick fix from the dashboard. They’re grouped below by where they show up. If you’re still stuck, see Getting help.

Signing in

You can’t sign in

  • Sign in with your work email — AcuSight routes you to your organization by email domain. A personal address may land you in the wrong place (or a brand-new empty org).
  • If your organization already exists, ask an admin to send you an invite rather than signing up fresh.
  • See Sign in & SSO for the available sign-in options.

You can’t see your team’s projects or devices

Organizations are fully isolated — you only see data in the org you’re signed into. If your workspace looks empty, you’re likely in a different org than your team. Sign out, sign back in with your work email, or ask an admin to invite you. See Organizations & multi-tenancy.

Devices

A device won’t come online after setup

Work through these in order:
  • Outbound internet — the device reaches AcuSight over HTTPS. It doesn’t need open ports, but it does need outbound access. Confirm it can reach the internet.
  • Docker — the agent runs in Docker. Make sure Docker is installed and the setup command can reach the Docker daemon; if not, re-run it with sudo.
  • A fresh setup command — setup commands are single-use and expire after 24 hours. Generate a new one from Devices → Add Device and run that.
Full walkthrough: Connect a device.

A device shows offline or “waiting”

Confirm the device has power and outbound internet. Devices reconnect on their own once they can reach AcuSight again — there’s nothing to restart manually. See Reliability for how recovery works, and Fleet management to inspect a single device.

Data

Images aren’t showing up

  • Make sure the device is assigned to a project and capturing — images arrive automatically as batches, first under a device’s Edge Data, then under Unassigned once added to a project.
  • A batch stays in collecting until it fills up or goes idle, then completes and is ready to annotate.
See Edge data collection and Projects & batches.

Training & models

Training won’t start or a job fails

  • Confirm the project has enough labeled images and that you’ve frozen a dataset version (snapshot) to train against.
  • Open the training job to watch its live status and logs — most failures surface there.
See Training & experiments.

A deployed model isn’t running on a device

Devices pick up a newly deployed model on their next check-in, so allow a moment after deploying. Then confirm the device is online and that you deployed to a group it belongs to. See Deploy a model.

Video

Live video won’t load

Live video streams peer-to-peer between your browser and the device. If a feed won’t load:
  • Confirm the device is online and running a model.
  • Refresh the Video page, or switch the device off and back on in the view.
  • Peer-to-peer works across networks — including behind NAT or a firewall — as long as the device has outbound access.
See Recording & livestream.

Co-Pilot

An answer looks wrong or incomplete

The Co-Pilot is read-only and scoped to your organization’s live data. If an answer seems off, rephrase the question or set an explicit time window (“last week”, “yesterday”) — it interprets time in your timezone. See the Co-Pilot tutorial.

Self-managed & on-prem

Running AcuSight yourself (self-managed, on-prem, or air-gapped)? Deeper operational troubleshooting — platform services, storage, identity, and networking — ships with the on-prem package and is supported directly. Contact your AcuSight representative.

Getting help

If you can’t resolve an issue from the dashboard, see Get help — the support channels, and what to include in a report so it can be acted on quickly.

Next steps

Connect a device

The full device onboarding flow.

Sign in & SSO

Sign-in options and organization routing.