# Sign-in troubleshooting

Nock sign-in has three stages: the desktop starts a request, the browser authenticates your account, and the result returns to the app. Identify where it stopped before changing settings.

## The browser page is unavailable

During launch preparation, public Nock account routes may not be deployed yet. A missing page can therefore be expected even when the marketing site loads. Check [Availability](/nock/availability). Reinstalling, clearing browser data, or creating another account will not publish an unavailable service.

When sign-in is available for your build, always start with **Sign in** inside Nock. A saved bookmark or old tab does not necessarily contain a current desktop connection request.

## The browser is signed in, but Nock is waiting

1. Confirm Nock is still running on the same computer.
2. Check whether the browser asks **Continue to Nock**. Verify the displayed account and continue only if you initiated this request.
3. Return to Nock and inspect its account state.
4. If nothing changes, start a fresh sign-in from the desktop app and use the new browser flow.

The handoff uses a temporary local callback. Old tabs can belong to requests that have already ended. Do not copy callback addresses between computers or send them to support.

## Too many attempts

For **Too many attempts**, wait a minute, then choose Sign in in Nock again. Avoid rapid refreshes or starting several simultaneous flows. If the service continues to fail, record the exact message and time and retry later.

Other messages such as **Could not reach V3Code** or **Nock couldn't be signed in** indicate a failed step, not proof that your password is wrong. Check connectivity and whether the account service is available before changing credentials.

## The wrong account appears

The browser may already be signed in to another V3Code account. Cancel an unexpected confirmation rather than continuing. Use the intended account in the browser and restart the Nock flow. Compare the account shown in the desktop with the one used for any checkout or access invitation.

## Signed in but still locked

Authentication and feature access are separate. Check the Plan and Unlocked sections of [Your account](/nock/account). Trial status, usage exhaustion, and feature rollout can all affect access after successful sign-in.

If checkout just completed, allow a minute for the account update and refresh. Do not complete another purchase solely to force access to refresh. Cloud-agent availability and hosted app-tool execution remain restricted during launch preparation.

## Report without exposing the handoff

Provide app version, operating system, browser, approximate time, the step that failed, and the visible error. Remove full callback URLs, authorization codes, tokens, and private account details from screenshots. See [Support](/nock/support).