# Browser troubleshooting

Nock's Web surface is a separate browser. Begin by identifying whether the problem is loading a page, showing it, signing in, or asking the agent to operate it. Each has different controls and restrictions.

## The address will not open

Check the exact URL. Nock accepts HTTPS websites and local development addresses. An ordinary remote HTTP site is blocked. Use the site's secure address when available; do not disable certificate checks to force a page open.

For a local preview, confirm the development server is running and that the host and port match. Open that same address in your normal browser. If both fail, inspect the local server before changing Nock. If only Nock fails, note its displayed error and whether a redirect changes the destination.

DNS failures, an offline connection, timeouts, and untrusted certificates are different failures. Save the message so a support report identifies the actual condition.

## The agent says it opened a page, but nothing appears

Check **Settings → Agent → Show browser while working**. When off, pages opened by the agent can remain in the background. Open **Web** and use **Show** to reveal the page.

Also check whether the page is floating in **PiP** or docked under the notch. **Dock** returns a floating page; **Expand** changes the docked size. Hiding or collapsing the surface affects visibility, not whether its task has finished.

## Sign-in or site features differ

Your normal browser's cookies and open tabs are not imported. Sign in yourself in Nock's browser where the site supports it. The agent's typing tool does not enter passwords. Glass Canvas web cards share Nock's browser profile, which can explain why a card is already signed in after using Web.

Downloads and website requests for camera, microphone, location, and notifications are disabled. A site depending on those features may not work here. Use your normal browser for those actions instead of repeatedly granting unrelated system permissions.

## Clicking or typing fails

The agent operates elements identified by its latest page read. Navigation, a dialog, or a dynamic refresh can invalidate those targets. Ask it to read the current page again before retrying. Describe the visible label and intended outcome rather than asking it to repeat an unexplained failed click.

After a submit action, inspect the resulting page or service state. A click completing is not proof that a purchase, upload, or form submission succeeded. Avoid repeating an uncertain transaction until you check.

## Mobile preview is different from a phone

Switch between **Mobile preview** and **Desktop preview** to inspect responsive layout. Mobile mode changes browser presentation and identification, but does not reproduce every physical phone capability. Test important mobile behavior on an actual device as well. See [The browser](/nock/browser) and [Privacy](/nock/privacy).