> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nerdit.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshoot the App

> Find a symptom, check its cause, and recover without changing unrelated state.

## Waiting for the machine to link

1. Confirm that you ran the link command on the machine where the Engine is installed.
2. If you used a App code, check its countdown. Use **New code** if it expired or was lost, then run the new displayed command.
3. If you used `nerdit link --device`, finish the approval in the correct Nerdit account and compare the terminal fingerprint.
4. Run `nerdit link` on the machine to inspect its link status. If the Engine itself is unavailable, follow [Engine installation and startup](/engine/installation).

Do not approve an unexpected request to make the waiting message disappear.

## Machine is offline

1. Check that the machine is awake, online, and running the Engine.
2. Inspect local Engine status and outbound connectivity using the [Engine networking guide](/engine/networking).
3. Wait for the App to observe the reconnect, then reload the machine page.

Offline means the App cannot reach the machine. It does not prove its workloads stopped. A directly served domain may still answer. Avoid unlinking a machine as the first response to a temporary outage.

## Machine not found

Return to **Machines** and check that you signed into the account that owns it. The machine may have been unlinked or the URL may be wrong. Use the current machine link from the list. If it was intentionally unlinked, [link it again](/app/connect-engine).

## Dashboard rejects a direct URL

Sign into the App, select the online machine, and use **Open dashboard**. This creates the browser session for that machine's dashboard. A copied machine URL alone does not grant access. If a previous dashboard session was revoked, open it again through the App.

## Services are missing or actions are unavailable

1. Read the message above the service list. A failed read, an offline machine, and an empty service list are different states.
2. Expand **Managed locally**. Those services require local administration.
3. Check the action's explanation. **Redeploy** requires an app with a Git source. **Roll back** requires a previous image.
4. If the list warns that it is incomplete, inspect all services directly on the Engine.

Use [Engine diagnostics](/engine/troubleshooting) for logs and build failures. The App's Activity page is not a runtime log viewer.

## Domain does not open or HTTPS fails

Open the app's **Domains** panel and choose **Check again**. Compare the DNS result, connectivity observations, and certificate message. A failed check does not remove a binding. Follow [Manage domains](/app/domains) and the [Engine HTTPS guide](/engine/networking); the App cannot fix DNS, CGNAT, or certificate prerequisites for you.

## Public app asks for sign-in

Check the app's confirmed public/private state, whether **Public access is paused**, and the account's plan status. Use **Resume** only when you intend to restore previously public apps. Public hosted access requires Pro and an eligible account. A direct custom domain has separate behavior and configuration.

## Assistant cannot connect or reach a machine

1. Use the URL and client ID currently shown in **Connect**.
2. If the page shows per-machine connections, use that machine's URL.
3. Check that the machine is online and, for an account connection, selected under **Machines this connection can reach**. Save any changes.
4. If access was revoked, authorize the connector again. If connection details are missing, contact support.

For permission refusals, check [Engine security](/engine/security). A remote assistant does not automatically receive local admin authority.

## GitHub repository is missing or deployment fails

Check that the GitHub integration is enabled, the account can deploy from GitHub, the GitHub App grants the repository, and **Machine access** includes it. Select an online destination. Recheck the chosen branch or tag and set any required secrets on the machine. Follow [Deploy from GitHub](/app/github) for the full flow.

## Get help

Contact [support@nerdit.ai](mailto:support@nerdit.ai) with the symptom, time, Engine version, failing action, and displayed error or request ID. Include whether the machine is online and whether local access works. Remove credentials, install codes, private repository details, secret values, and personal data from screenshots and logs.