cloudflare-troubleshooting

1# Cloudflare Troubleshooting
2 
3> **Methodology base:** the general evidence-driven network-diagnosis discipline (falsification, layered isolation, counter-review) lives in the **debugging-network-issues** skill. This skill is the Cloudflare *domain* layer on top of it.
4 
5## Core Principle
6 
7**Investigate with evidence, not assumptions.** Always query Cloudflare API to examine actual configuration before diagnosing issues. The skill's value is the systematic investigation methodology, not predetermined solutions.
8 
9## Investigation Methodology
10 
11### 1. Gather Credentials
12 
13Reuse the domain and authorized Cloudflare connection already supplied by the user or project configuration. Ask only for missing connection information: domain, account email plus Global API Key, or API Token. Keep the working authentication method; troubleshooting does not require replacing it.
14 
15Global API Key location: Cloudflare Dashboard → My Profile → API Tokens → View Global API Key
16 
17### 2. Get Zone Information
18 
19For zone-scoped troubleshooting, obtain the zone ID:
20 
21```bash
22curl -s -X GET "https://api.cloudflare.com/client/v4/zones?name=<domain>" \
23  -H "X-Auth-Email: <email>" \
24  -H "X-Auth-Key: <api_key>" | jq '.'
25```
26 
27Select the exact matching zone and account before extracting its `id`; do not blindly select the first result when account or domain identity is ambiguous. Use that zone’s `account.id` for account-scoped calls.
28…