Troubleshooting

Deployment failed

• Cloudflare connection: if access was revoked, click Connect Cloudflare to reconnect, then retry.
• Auto DNS mode: automatic DNS uses the Zone and DNS access from your Cloudflare authorization. If it fails, switch to manual DNS.
• Workers subdomain: the wizard checks this for you. If it reports that workers.dev is missing, configure a workers.dev subdomain in Cloudflare's Workers & Pages dashboard, then reconnect.
• Wrong account: if you have access to more than one account, confirm you picked the right one when connecting.

Monitor checks fail unexpectedly

• Ensure targets are publicly reachable from Cloudflare.
• Match method/target format (http(s)://... for HTTP methods, host:port for TCP_PING).
• Confirm expected status code is correct.
• Use Test Endpoint in wizard before deploy.

Custom domain not working

• Verify the exact CNAME target shown in the wizard/deploy output.
• For manual mode, ensure DNS record type/name/target are correct.
• For auto mode, ensure the zone is in the connected account and your authorization covers DNS access.
• Allow a few minutes for DNS/SSL propagation.

Webhook notifications not arriving

• Use the wizard Test Webhook button first.
• Confirm endpoint URL and destination-side auth/rate limits.
• Inspect payloads with webhook.site.
• If destination expects another format, add a small transformer endpoint.

First request feels slow

A cold start can happen after inactivity. Subsequent requests are typically faster.

Deleting a deployment

Preferred path: use the delete flow in the post-deploy screen (includes optional KV deletion).

If config metadata is unavailable, delete manually in Cloudflare dashboard:

1. Remove status page + monitor workers.
2. Remove flarewatch-config and flarewatch-state KV namespaces (optional, destructive).
3. Remove custom-domain DNS records you created.

License issues

• License key not accepted -- Check that the format matches what you received from Polar. Verify the license is activated in your Polar account. Copy-paste the key directly to avoid extra whitespace.
• License already linked to another Cloudflare account -- Delete the current deployment from that account to release the license, or reconnect the account shown in the error. Same-account redeploys reuse the existing license link.
• License expired -- Your existing deployment continues to run. License renewal is only needed to access newer runtime artifacts and wizard features.

Status page issues

• Admin login not working -- Re-deploy with the wizard to reset authentication secrets. Connect to the same account and load existing config. This updates auth credentials without affecting your monitors or history.
• Status page shows no data -- The monitor worker runs on a cron schedule (every 5 minutes by default). After initial deployment, allow up to 5 minutes for the first check to complete and populate data.

SSL certificate pending

Cloudflare automatically provisions SSL certificates for custom domains. This typically takes a few minutes but can occasionally take longer. Check the SSL/TLS section of your domain in the Cloudflare dashboard to see the certificate status. If provisioning stalls, verify that your CNAME record is correct and pointing to the right Workers route.

Need more help?

If the issue persists, email support@flarewatch.app.

Include a short summary, the exact error text, and your status page URL if available.

Do not include Cloudflare credentials, passwords, or secret keys.