Find the outcome you need.
Start with a symptom, a platform or the thing you want working.
With JavaScript, search filters the whole collection in your browser. Without it, use the linked pages and section navigation below; query filters need JavaScript.
Showing entries 801–840 of 1179 in this first collection.
Inspectable example
Example: a verification record for restoring a hacked WordPress site
A synthetic record showing a timeline, why one backup was chosen, checksum output, unexplained files, an administrator review and a credential reset list, with a plain statement of what it does not prove.
Troubleshooting guide
Bare domain or www not opening? Check the record at each name before touching the website
The bare domain and the www address are separate DNS names with separate answers. Learn why a CNAME at the bare domain is a trap and how to see what each name returns.
Troubleshooting guide
Too many redirects behind Cloudflare: find which two settings disagree
A redirect loop means two rules each send the visitor where the other forbids. Read Cloudflare's encryption modes and find the pair that disagree before changing anything.
Troubleshooting guide
Padlock missing after switching to HTTPS? Find the http resources still loading
A page served over https that loads some files over http is mixed content. Learn what browsers upgrade or block, how to find the leftover http links, and what actually fixes them.
Troubleshooting guide
Old or wrong page showing behind Cloudflare? Read the cache status before purging
Stale or shared pages behind Cloudflare usually come from a rule or header, not from time. Learn the defaults, read the cache status values and test safely before you purge.
Troubleshooting guide
Uptime alerts that mean something: what to check, from where, and who gets told
A status-only check can pass while your page shows an error. See how uptime checks decide pass or fail, what to add, and how to prove an alert reaches two people.
Troubleshooting guide
Domain expiry and registrar lock: what the status codes mean and what you can still do
ICANN publishes what each domain status means, from the transfer lock to redemption and deletion. Learn which are in your control, which are not, and how to check yours.
Troubleshooting guide
Old DNS records that point at services you no longer use: why to remove them safely
A record that still points at a cancelled service can let someone else claim that name. Learn what dangling DNS is, how to review a zone, and which old-looking records must stay.
Troubleshooting guide
Mail to your domain not arriving? Read the MX records before blaming the mailbox
MX records tell the world where to deliver your mail. Learn how priority works, why the name inside an MX record must not be an alias, and how to compare yours with the provider's.
Troubleshooting guide
After moving email away from your web host, check the host's mail routing setting
On cPanel-style hosting the server can decide it is your mail server. Learn how local, backup and remote routing differ, and why website mail to your own domain can vanish after a move.
Troubleshooting guide
Read the bounce message first: what each part of an email failure tells you
A bounce message names the failing step. Learn how enhanced status codes such as 5.1.1, 5.1.2 and 5.7.x split address, domain and policy faults before you change any DNS.
Troubleshooting guide
Why forwarded email gets rejected or junked, and what to use instead of a forward
A forward resends mail from your server, which can break SPF, alignment and DKIM at the final receiver. See what each provider documents, and when an alias or shared mailbox is safer.
Troubleshooting guide
Moving Google Workspace mail to Microsoft 365: what happens to Gmail labels, and what you can leave out
Gmail labels are not folders, and one message can carry several. Decide what to leave out, run a pilot to see how labels arrive, and learn what Microsoft's migration does and does not document.
Troubleshooting guide
Moving a WordPress site: the files, the database and the web address stored inside it
A WordPress move copies two things and sometimes rewrites a third. Learn when the address must change, why a blind find-and-replace corrupts settings, and how to test before DNS.
Troubleshooting guide
WordPress hardening: what each common measure does, what it cannot do, and a safe order
WordPress's own hardening guide calls its measures risk reduction, not elimination. Learn what each does, which caveats apply, and an order that protects you from breaking the site.
Troubleshooting guide
Hacked WordPress site: restore a clean backup or clean in place, and what a restore cannot do
WordPress's own advice for a hacked site starts with documenting, resetting passwords and fresh files. Learn what checksum checks can and cannot prove and when to stop and take advice.
Platform
Cloudflare for a small business: separate the DNS record, the proxy, the encryption mode and the cache
Cloudflare faults are usually in one of four layers. Learn what proxied and DNS-only mean, why mail records stay DNS-only, and which fixed-price jobs fit which layer.
Platform
cPanel-style hosting: what lives in the account, where mail routing is decided and what a backup restores
On cPanel hosting a website, its database, its mail and its DNS zone sit in one account. Learn how mail routing is detected, what the backup tools can restore, and where our jobs fit.
Platform
Microsoft 365 email for a small business: the DNS records, the switch-over and the forwarding setting
Exchange Online needs a short list of DNS records, one SPF record and a careful MX switch. Learn what Microsoft documents, how forwarding is controlled and where our email jobs fit.
Platform
Google Workspace email for a small business: the MX record, labels, forwarding and sender rules
Google Workspace uses one MX record, treats labels as folders over IMAP, separates forwarding from redirecting and sets sender rules for mail to Gmail. Learn what Google documents and where our jobs fit.
Troubleshooting guide
A browser test fails when the page is slow: wait for a condition instead of pausing for a fixed time
Read a Playwright timeout as a question about which condition was not met, use the waiting the tool already does, and stop lengthening pauses that still fail on a slow day.
Troubleshooting guide
Browser tests pass alone and collide when run together: give each test its own account and data
Separate what Playwright isolates in the browser from the server-side data that parallel workers still share, and use per-worker accounts and unique identifiers to stop tests interfering.
Troubleshooting guide
A browser test passes on your laptop and fails in CI: collect a trace before changing anything
Capture evidence from the failing CI run with Playwright's trace viewer, compare the environment differences that matter, and change one thing at a time instead of loosening the test.
Buyer collection
For an engineering manager: decide what is wrong with the safety net before buying anything
Tell apart a suite nobody trusts, code nobody can safely change and an app nobody can see into, then pick the smallest bounded job that answers the one you actually have.
Buyer collection
For an agency or founder handing over a codebase: what to check so the next owner can run it
Before a codebase changes hands, check that a stranger can start it, that its dependencies are not an open list of known advisories, that no secret rides along and that someone independent has read the latest changes.
Collection
When the test suite cannot be trusted: work out which kind of unreliable it is, in this order
An ordered diagnosis from checking that the failure is real, through shared state, time and randomness, waiting and CI differences, to what to do with a test you cannot fix yet, linked to guides and bounded jobs.
Collection
When you hear about production errors from customers: build the view in this order
An ordered map from capturing exceptions, through readable traces and safe payloads, to one trusted alert and a request ID that links the alert to log lines, with the guide and bounded job for each step.
Troubleshooting guide
Before refactoring an untested module, record what it does today with characterisation tests
Record the behaviour a module has now, without deciding whether it is right, and learn what a coverage figure does and does not tell you about the safety net you just built.
Troubleshooting guide
npm audit reports a vulnerable package you never chose: fix the parent before you reach for force
Read an npm audit report as a dependency path, apply fixes in order of safety, treat an override as a narrow temporary pin and keep a forced major update a decision rather than a default.
Troubleshooting guide
pip-audit reports a vulnerable Python package: separate the fixable findings from the pinned and the unfixed
Know what pip-audit examined, preview a fix before applying it, handle findings that have no fixed version and run the audit in an isolated environment.
Troubleshooting guide
A secret was committed to git: revoke it first, then decide whether to rewrite history
Order the response to a committed credential correctly: revoke, remove it from the code, decide on a history rewrite and its limits, and stop the next one with ignore rules and push-time scanning.
Inspectable example
Example stabilisation ledger for five flaky tests, with how to read the run counts
An inspectable synthetic ledger of five tests showing baseline failures and rates, classified causes, fixes, a not-reproduced test and an approved open quarantine, with how the required run count is worked out and what a clean run count can and cannot show.
Inspectable example
Example definition of three critical flows for a browser smoke suite, with break checks
An inspectable synthetic definition of three flows with start, steps, observable end state, data, third-party handling and the deliberate fault that must make each test fail.
Inspectable example
Example rotation checklist for a committed access key, with what the account holder does
An inspectable synthetic checklist in the order a rotation should happen: revoke, replace, configure, verify, review logs, find copies and only then clean the repository.
Inspectable example
Example written review of one pull request: findings, labels and a not-examined list
An inspectable synthetic review of an invented pull request showing the five parts of a finding, the shown and suspected labels, and the list of what was not examined.
Troubleshooting guide
Error reports show minified code: make stack traces readable with source maps
Work out why an error tracker shows bundled, minified lines and check that the build, the upload and the deployed code agree, using a deliberate test error rather than waiting for a real one.
Troubleshooting guide
Check what your error reports contain before launch, and filter sensitive data at the source
Find out what an error event carries beyond a stack trace, choose where to scrub it, use a before-send hook and test the filter with invented secrets before real traffic arrives.
Troubleshooting guide
An error tracker that alerts on everything gets muted: tune grouping and alert rules
Understand how events are grouped into issues, why one fault becomes many issues, and how to build one alert rule that tells the right person about the right thing.
Troubleshooting guide
Follow one request through your logs: structured records and a request ID in Python
Turn free-text log lines into records a program can parse and attach a request identifier with filters and context variables so every line from one request can be found together.
Troubleshooting guide
One slow endpoint or page: measure the distribution before you change any code
Build a measurement two people would agree on, read percentiles instead of averages, separate lab from field figures and decide what a believable before and after comparison has to show.