Certbot DNS SERVFAIL: inspect domain and CNAME resolution
Trace A, AAAA and CNAME answers to the authoritative servers when Certbot fails with DNS SERVFAIL.
KAN KAI WORKS · Help
Automation and access can fail at several handoffs: the trigger, a queue, a permission check, the connection or the destination system. Select a guide using the product and exact message. A manual test and a real production run may follow different paths.
These guides cover different systems and causes. Match the product, operating mode and version to the individual case, then verify the result at the actual destination.
Trace A, AAAA and CNAME answers to the authoritative servers when Certbot fails with DNS SERVFAIL.
Check the actual Certbot executable, authentication method and scheduler separately before a certificate expires unnoticed.
Identify the unsupported authenticator combination and plan a renewable DNS challenge for your wildcard certificate.
Compare the public response, connector and origin separately.
Separate resolver reachability, DNS policy and UDP/TCP behaviour when WARP can no longer resolve internal names.
Distinguish UDP reachability from a successful QUIC handshake and run a limited HTTP/2 comparison where appropriate.
Check name resolution inside the connector environment when a .local service works on other devices.
Trace Location headers and the origin scheme when an application enters a redirect loop through the tunnel.
Compare saved remote configuration, expected units and elapsed time when an origin request times out immediately.
Trace the WebSocket handshake to the origin when live updates fail but ordinary HTTP requests still work.
A later Stock Reconciliation blocks an earlier batch entry? Inspect document chronology, affected batch and version before changing records.
Installation requires incompatible Tenacity 8.2 and 9.1 ranges? Compare exact app revisions and dependencies instead of forcing alternating versions.
CRM assets fail with MISSING_EXPORT after a Frappe update? Compare the component interface and matching CRM version before applying local patches.
Compare IPv4 and IPv6 on the same challenge path when the website works but certificate renewal fails.
Compare the same challenge path from independent networks and match both successful and missing requests to your logs.
Opening a webhook URL returns Unauthorized? Check its API-key header, IP rules and actual hook identity without removing protection.
A Google connection exists but Sheets or Drive return 403? Separate OAuth completion, connection identity and access to the actual file.
An incomplete Make execution fails at an aggregator? Inspect saved run state, Source Module and data completeness before restarting.
Several spreadsheet rows but one result? Compare spreadsheet ID, sheet, range and the actual module output before downstream filters.
curl works but Make returns a parameter-validation error? Compare the transmitted JSON body, headers and resolved values.
The source contains several items but Iterator receives nothing? Check the field path, array type and module reference in the same execution.
Separate request arrival, execution storage and the target system.
An n8n run failed after the target already processed its request? Reconcile business references and retry behaviour before repeating the action.
n8n cannot reach an HTTPS API that opens in your browser? Separate connection establishment, source network and HTTP response.
Postgres connection fails with a certificate-chain error? Check the endpoint, trust chain and the differences between Cloud and self-hosting.
Item links fail after Get row(s)? Check match counts, empty results and business IDs before data is assigned to the wrong record.
429 or concurrency errors after n8n branches converge? Inspect node invocations, item counts and the intended aggregation separately.
Publication reports an existing name after deployment? Compare the running n8n version with database migration history before duplicating workflows.
Scheduled processing goes quiet? Check publication, timezone and expected business output, then monitor missed successful runs.
Blank n8n editor or repeated disconnects? Separate browser, connection and backend health without replaying active operations.
Instagram test events work but real messages are missing? Trace event delivery, the public route and the n8n production endpoint.
Executions remain queued or the instance restarts? Inspect backlog, active runs and workload before replaying incoming events.
A corrupt SQLite database stops n8n? Preserve the original, companion files and key, then assess recovery on an isolated copy.
A hostname fails to resolve from n8n? Inspect container DNS, service names and destination ports in the relevant network.
Assess needsDbUpgrade and an already existing table safely.
Saving fails with Sabre DAV Locked? Identify the lock mechanism and distinguish it from filesystem permissions before removing anything.
An update stops at its write-permission check? Identify the exact path, effective PHP user and mount permissions before changing ownership.
Upload limits or PHP values remain unchanged? Compare web SAPI, CLI and the configuration actually loaded before reinstalling PHP.
Office connection appears healthy but documents will not load? Check browser access and both server-to-server connection directions.
Team files remain on storage but folders disappear from Nextcloud? Check app state, folder configuration and group access before recreating them.
Unknown files detected within the installation folder? Identify the reported files and preserve evidence before cleaning the installation.
Files disappear after a mount or sharing change? Pause synchronisation, preserve local copies and establish server and storage state.
Reading works but saving returns Permission denied? Distinguish a local bind mount from SMB access and identify the effective writing identity.
AIO reports a domain or reverse-proxy problem? Check DNS, APACHE_PORT and the upstream actually reachable from the proxy.
Compare nginx’s certificate path with the actual file, startup directory and permissions before issuing replacement certificates.
Check the DuckDNS response, domain ownership and published TXT record when SWAG cannot renew its wildcard certificate.
Separate the DSM message from a confirmed ACME rate limit and check domain validation and certificate assignment.
Identify the OAuth client and preserve existing backups before authorising the Drive connection again.
Check the bootstrap file, actual website path and PHP configuration in the correct order.
Choose an authorised owner-recovery route and fully re-establish two-factor protection afterward.
Explore all 100 troubleshooting guides →
Describe the affected system, the visible problem and when it started. That gives us a starting point for the next check.
Describe a different issue →