Troubleshooting

The most common problems and their fixes. If your issue isn’t here, check the FAQ or contact support.

Can’t find or connect to your rig

The rig doesn’t appear in the list of rigs

1. Same network? Your phone/tablet and the rig must be on the same network for local discovery. Guest Wi-Fi networks and VPNs often isolate devices from each other — join the main network and turn off any VPN.
2. Give the scan a moment. Discovery uses mDNS with a subnet sweep as backup; the sweep can take a few extra seconds on large networks.
3. Go direct. Open http://<rig-name>.local:8080 in a browser (for example http://aris-pi-ai.local:8080) — every rig serves the app itself. 8080 is the default port; if you changed it with the pencil next to the rig’s name in Settings → Connection, use yours. If that loads, the rig is fine and the issue is discovery on your network.
4. IP fallback. If .local names don’t resolve on your network, find the rig’s IP address (from your router’s device list). On the connection screen tap Open Array, then under Connect to Agent enter the address in Host and the port in Port (once the Array holds a rig, these fields are under Add Rig).
5. Is the rig on? Confirm the rig computer has power and its network light is active. It can take a minute after power-on for the backend to come up.

“ARIS cannot pair this device with the rig”

A rig flashed with ARIS Rig OS asks each phone, tablet and browser to sign in once after it has been claimed for remote access; a hand-installed rig, a NINA rig and an unclaimed rig never ask. A device that has not signed in gets this message. Open Settings (the gear) → Account & Sync → Sign In / Create Account, sign in with the account that claimed the rig, and connect again — the device and the rig both need internet for this one sign-in. If it then says the rig accepts this device in up to 60 seconds, wait a minute and try again. See Sign in.

One rig, one entry

Recent Connections shows one entry per physical rig, however many ways you’ve reached it — the .local name, a raw IP, a remote route all collect inside that rig’s single entry, and connecting uses the best route available. If you remember the same rig appearing under three different addresses, that’s the old behavior; now you pick the rig, not an address.

Understanding connection states

The connection banner shows live health:

• Healthy — connected and communicating normally.
• Reconnecting — the connection dropped and ARIS is restoring it automatically (it retries several times with increasing delays). Brief Wi-Fi hiccups resolve themselves here.
• Degraded — repeated reconnects have failed. Check that the rig is powered and reachable (try its direct URL), then reconnect manually.

Note

A running sequence does not depend on your connection — the rig executes it locally. If your app disconnects mid-sequence, reconnect and you’ll pick up the live state exactly where it is.

App looks stale or broken after an update

In the browser: the web app caches itself for offline use, so right after we ship a fix your browser may keep showing the old version. Do a hard refresh — Cmd+Shift+R (Mac) or Ctrl+Shift+R (Windows/Linux), or hold the reload button and choose “Empty Cache and Hard Reload”. That clears the cached app and loads the new one.

In the iOS/Android apps: updates download in the background. When you see “Update downloaded — restart ARIS to apply.”, close and fully reopen the app. Settings → About → Software shows your current version and patch number — useful when reporting an issue.

“App is too old for your rig” (or the reverse): the app and rig check versions against each other and the message says exactly which side to update — follow it.

Remote access problems (beta)

Can’t reach a rig away from home? Check in order:

1. Signed in — with the same account? Remote access is tied to the account that claimed the rig. Sign in with the same account every time.
2. Is the rig online? Your fleet list shows live presence. If the rig shows offline, it has no internet at its site (or is powered off) — remote control needs the rig online; your home LAN connection never does.
3. Re-pair if needed. If a rig has fallen out of your fleet, open Settings → Connection → Remote access on the rig’s network and claim it again — see Pair for Remote Access.

Guiding won’t start

• ARIS gives PHD2 up to 90 seconds to start, begin looping, and lock onto a guide star. If that window passes, you’ll get an honest failure rather than a silent hang — usually it means no usable star (clouds, cover closed, focus way off) or a guide camera problem.
• Open the notification bell: guiding alerts include one-tap actions, including Restart PHD2, which cleanly restarts the guiding process on the rig — the fastest fix for a wedged guider.
• Check the guide camera is connected and the guide exposure is reasonable (1-3 s); very short exposures find fewer stars.

Camera and capture issues

• Captures timing out or downloads stalling: lower the camera’s USB bandwidth setting, especially with multiple cameras sharing one hub, or move the guide camera to a different port.
• Camera vanished mid-session: reseat the USB cable — the rig detects unplug/replug automatically and recovers the device.
• Images black: check exposure and gain, and confirm a flat-panel cover isn’t closed (during sequences ARIS auto-opens it before light frames).

Getting help

• Settings → Advanced → Driver Diagnostics shows each driver’s status and the equipment connection in one place — include what it says when you report an issue.
• Contact support with what you did, what you expected, what happened, a screenshot if you have one, and roughly when it happened — the time lets us match it to the rig’s logs.