Short ANT

Find the issue before changing settings.

Connection errors, usage limits and account restrictions are different problems.

Read the error and check results before reinstalling or changing your setup.

A simple troubleshooting flow

  1. 1CheckCollect observations
  2. 2ReviewSeparate issues from unknowns
  3. 3AdjustChange one setting at a time
  4. 4RecheckVerify the relevant results

First, identify the problem

1.

The website works, but Claude Code does not

Check browser and terminal connectivity separately.

Connectivity
2.

You see a usage limit or a busy-service message

Read the error before assuming your account is banned.

Errors & limits
3.

You received an account suspension notice

Follow the official notice and review the appeals guidance.

Account help
Back up first. Change one setting at a time, then recheck or restore.

Let your agent help troubleshoot

Read-only checks first. Review proposed changes before applying them.

Read with your agent · Markdown
Scope and safety before configuration

Before changing anything

Identify the operating system, client version, launch entry and actual execution host. A working browser does not verify a terminal, IDE, remote host or child process.

Choose whether the goal is known-destination routing or isolation of an entire workload. Record unknowns; these are different guarantees.

  • Keep existing account mode, ordinary networking and remote access.
  • Prepare a scoped backup and a recovery path before edits.
  • Never send credentials, full logs, subscriptions or personal configurations to this site.

What this website can verify

The check observes the current browser connection. Its score cannot verify Claude account permissions, CLI isolation, DNS routing or a future ban. Local configuration and failure recovery require separate authorized checks.

Sources and scope

2026-11-05 · Public Network Protection Guide 3.0.1