Practical WordPress and website diagnostics covering hosting, DNS, SSL, errors, performance, publishing, media, email, security, and site management. Guides focus on identifying the failing layer before changing settings.
DNS_PROBE_FINISHED_NXDOMAIN means the DNS lookup says the requested hostname does not exist. The browser has not reached WordPress yet, so plugins and themes are not the place to begin. Copy the exact hostname from the failed address, check its spelling and find the DNS zone currently authoritative for it. The root domain and www name … Read more
Seeing DNS_PROBE_POSSIBLE soon after a DNS move suggests the new delegation or records may not yet produce a consistent answer. Use the recent change as evidence rather than changing WordPress settings at random. Begin with the exact hostname that fails, then compare the active nameservers and essential records with the previous working setup and the … Read more
Cloudflare error 1116 appears while a domain is being added, before ordinary website traffic uses the proposed Cloudflare configuration. That makes the submitted domain name the first thing to inspect. Enter the registered main domain rather than a full website URL, page path or subdomain. Keep the existing DNS connection working until Cloudflare accepts the … Read more
Cloudflare error 1097 is an onboarding restriction, not a WordPress file error. Changing plugins, themes or database settings will not establish why Cloudflare declined the domain addition. Preserve the complete message and prepare a concise review request that explains your relationship to the domain, its current registration status and the setup step that produced the … Read more
Cloudflare error 1099 means the submitted name was not recognized as a registered domain during setup. It does not by itself show that the live WordPress site, hosting account or individual DNS record is broken. Compare the value entered in Cloudflare with the exact domain and status shown by the registrar. Use the registered apex … Read more
Cloudflare error 1110 occurs while the onboarding system is trying to look up registration or hosting information for a domain. The useful evidence is the submitted name, the registrar’s current status and the full message returned by Cloudflare. Check those items before repeatedly retrying or changing DNS records. A lookup failure during onboarding is separate … Read more
Cloudflare error 1050 can appear when an Access account uses a default-deny policy but the requested hostname does not match an Access application. The request is stopped at Cloudflare before it reaches the WordPress login screen. Decide who should reach the hostname, then compare it with the application domain and policies configured in Cloudflare Access. … Read more
Cloudflare error 1047 needs its complete message and request context before a reliable repair can be chosen. The number alone does not identify one universal WordPress, DNS or Worker fix. Record the hostname, affected action, time and last relevant configuration change. Then determine whether the failure applies to one route, one Cloudflare feature or the … Read more
Error 1049 during setup concerns recognizing the submitted domain as registered. Compare the exact name and current registrar status before changing WordPress. Hosting, registration and DNS are separate launch steps. A temporary website working does not establish that the custom domain is ready for onboarding. Guide reviewed: October 8, 2026. Interface labels may vary by … Read more
A Worker can handle a request before WordPress receives it. For error 1100, identify whether that hostname and path are covered by a Worker, then use the full message and invocation evidence. Do not assume the code means a CPU limit or an exception without supporting detail. Compare the affected operation with the deployment and … Read more