Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- A and AAAA records show DNS answers, not which route the request actually used.
- An unauthenticated 404 proves only that a request reached HTTP, not identity or resource access.
- Append IPv4-first only to the current PowerShell process and restore NODE_OPTIONS in finally.
- One Wrangler 4.158.0 observation is not a universal Windows or Node networking fix.
Separate the network phase from identity
When a Windows Wrangler 4.158.0 API request fails, first confirm Node and Wrangler versions and whether failure occurred during name resolution, TLS, or an HTTP response. A public static page loading does not prove the API route works. A 401, 403, or 404 means an HTTP response was reached, but says nothing by itself about login, permissions, or resource access.
Keep only a redacted status, time, and tool version. Do not copy an access token, OAuth authorization code, account ID, email, request headers, or full logs containing a private hostname.
Check A and AAAA records and the Node version
Query A and AAAA records for the public API host separately and note which IPv4 and IPv6 addresses DNS returns. The presence of both records does not prove the client tried them in a particular order or that either address is reachable; DNS answers are only one piece of evidence.
Record the Node and Wrangler versions. This guide is limited to one Windows observation with Wrangler 4.158.0. Node’s DNS default order depends on version and startup options. Consider the process-scoped dns-result-order option only when the installed Node version supports the option documented by Node.js.
Use an unauthenticated 404 only to confirm HTTP reachability
A request without a token to a documented read-only path can distinguish DNS/TLS/connection failure from an HTTP response. A 404 means only that an HTTP server was reached and the path did not match. It does not validate a Cloudflare identity, token scope, or deployment permission.
If the request times out or fails certificate or name resolution checks before a response, investigate the route, system trust store, and DNS separately. Do not disable TLS verification or treat an unauthenticated 404 as an API fix or account check.
Check HTTP reachability without credentials
powershellcurl.exe --connect-timeout 10 --max-time 20 --silent --show-error --output NUL --write-out "%{http_code}\n" "https://REPLACE_WITH_PUBLIC_API_HOST/REPLACE_WITH_DOCUMENTED_READ_ONLY_PATH"
Query the public API host A and AAAA records
powershell$publicApiHost = "REPLACE_WITH_PUBLIC_API_HOST"
Resolve-DnsName -Name $publicApiHost -Type A
Resolve-DnsName -Name $publicApiHost -Type AAAA
Protect output while checking identity and scope
After the network layer returns a response, use Wrangler’s read-only identity check to confirm the active authorization context. Have the account owner verify the target resource and minimum required scope. The command may show an email, organization, or account detail, so inspect it only in a trusted terminal and share only a redacted pass/fail state with support.
If the source of an environment token or local login state is unclear, do not configure multiple credentials or borrow a colleague’s OAuth identity. If rotation is required, confirm the caller, required permissions, and revocation plan before using Cloudflare’s official security flow.
Test IPv4-first for one child process only
If both A and AAAA records exist and evidence points to this Node process’s resolution order, save whether NODE_OPTIONS existed and its exact value in the current PowerShell process. Append dns-result-order=ipv4first and run one read-only whoami check. The finally block must restore the exact prior state: remove the variable if it was originally absent, or restore its original value if it was present.
This affects only Wrangler processes started by the current PowerShell process; it does not write user- or system-level settings. It does not disable IPv6 or prove which route caused the failure. Restore it immediately and never put the temporary value into a config file or persistent shell profile.
Append and restore NODE_OPTIONS for this process
powershell$nodeOptionsWasSet = [Environment]::GetEnvironmentVariables('Process').Contains('NODE_OPTIONS')
$previousNodeOptions = [Environment]::GetEnvironmentVariable('NODE_OPTIONS', 'Process')
try {
$dnsOption = '--dns-result-order=ipv4first'
if ([string]::IsNullOrWhiteSpace($previousNodeOptions)) {
[Environment]::SetEnvironmentVariable('NODE_OPTIONS', $dnsOption, 'Process')
} else {
[Environment]::SetEnvironmentVariable('NODE_OPTIONS', "$previousNodeOptions $dnsOption", 'Process')
}
wrangler whoami
}
finally {
if ($nodeOptionsWasSet) {
[Environment]::SetEnvironmentVariable('NODE_OPTIONS', $previousNodeOptions, 'Process')
} else {
[Environment]::SetEnvironmentVariable('NODE_OPTIONS', $null, 'Process')
}
}
Keep the observation bounded to this environment
The observation is limited to one API check on Windows with Node.js and Wrangler 4.158.0. A request succeeding after IPv4-first can be recorded as that result at that time; it does not show that all Cloudflare APIs, accounts, networks, or Node versions will recover. It does not establish IPv6, DNS, or proxy as the earlier root cause.
If the temporary check changes nothing, restore the variable and continue checking identity, resource permissions, proxy, and official service status separately. If the result changes, restore the variable and repeat the same read-only request once. Do not blindly retry an uncertain remote business operation.
Sources
Frequently Asked Questions
Does a 401 or 404 from the API root mean the network is down?
Not necessarily. Receiving an HTTP status usually means DNS, TLS, and HTTP reached a response. It does not validate authentication or a specific API route.
Can I attach raw wrangler whoami output to a support ticket?
Do not share the raw output. It may include email, organization, or account details. Share only a redacted pass/fail state and necessary error class.
Should I grant every permission when replacing a token?
No. An authorized owner should check the minimum scopes required for the current task and plan how the old token will be revoked.