Error reference changederrors
Nearest release: v2.1.238, published 8 hours before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+27added
Lines−0removed
From line
79
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits187to this page, all time
The whole hunk
from line 79, old and new numbered
/
from line 79
7979| `SSL certificate verification failed` | [Network](#ssl-certificate-errors) |
8080| `SSL certificate error (...)` during login or startup | [Network](#ssl-certificate-errors) |
8181| `403` with `x-deny-reason: host_not_allowed` in a cloud or routine session | [Network](#host-not-allowed-in-a-cloud-session) |
82| `proxy refused the connection` | [Network](#the-proxy-refused-the-connection) |
8283| `403` with `This GraphQL query is not enabled for this session` in a cloud session | [GitHub proxy](/docs/en/cloud-environments#github-proxy) |
8384| `Couldn't reconnect to your Remote Control session` | [Network](#couldnt-reconnect-to-your-remote-control-session) |
8485| `N sessions ended while this machine was offline — the environment was cleaned up on the server and can't be resumed.` | [Network](#sessions-ended-while-this-machine-was-offline) |
from line 1103
11021103* Click **Save changes**. The next run uses the updated allowlist.
11031104
11041105See [Network access](/docs/en/cloud-environments#network-access) for access levels and the default allowlist. Local CLI sessions are not affected by this policy.
1106
1107<h3 id="the-proxy-refused-the-connection">
1108 The proxy refused the connection
1109</h3>
1110
1111You see this message when Claude reads an [artifact](/docs/en/artifacts) through the proxy you set in `HTTPS_PROXY` or a related [proxy variable](/docs/en/network-config#environment-variables). Artifact content comes from `*.frame.claudeusercontent.com`, so Claude Code first sends the proxy a `CONNECT` request asking it to open a tunnel to that host. When the proxy refuses, nothing reaches the host, and the message carries the proxy's HTTP status:
1112
1113```text theme={null}
1114artifact content fetch failed (proxy refused the connection: HTTP 407)
1115artifact content fetch failed (proxy refused the connection: HTTP 403)
1116the proxy refused the connection to the artifact's content host (HTTP 502)
1117```
1118
1119The status is the proxy's answer to the `CONNECT`. The host never answered, so each status points at a different fix:
1120
1121* `HTTP 407`: the proxy requires credentials it didn't get. Put them in the proxy URL, as [Basic authentication](/docs/en/network-config#basic-authentication) shows.
1122* `HTTP 403`: the proxy refuses to tunnel to `*.frame.claudeusercontent.com`. Ask whoever runs the proxy to allow that host, which [Network access requirements](/docs/en/network-config#network-access-requirements) lists.
1123* Any other status, such as `HTTP 502`: the proxy didn't open the tunnel for its own reason, such as failing to reach the host. Look the status up in the proxy's logs.
1124* `unreadable reply` in place of a status: whatever is at the proxy address didn't answer with an HTTP status line. Check that the address is an HTTP proxy.
1125
1126**What to do:**
1127
1128* Check the address and credentials in the proxy variable, as [Proxy configuration](/docs/en/network-config#proxy-configuration) describes, then run `curl -x http://proxy.example.com:8080 -I https://api.anthropic.com` from the shell you start Claude Code in, using your own proxy URL. On Windows PowerShell, run `curl.exe`. If this probe fails the same way, fix the proxy setup first. If it succeeds, the refusal is specific to the artifact host.
1129* If your network lets Claude Code reach the artifact host directly, add `.claudeusercontent.com` to [`NO_PROXY`](/docs/en/network-config#environment-variables).
1130
1131Before v2.1.238, Claude Code reported a refused tunnel as a generic network error.
11051132
11061133<h3 id="couldnt-reconnect-to-your-remote-control-session">
11071134 Couldn't reconnect to your Remote Control session
No line in this hunk matches that.