Browse the docs

Troubleshooting

What to do when an ownership check misses your proof or a firewall challenges SiteCMD, and how each of SiteCMD's requests names itself in your logs.

Most problems with SiteCMD come down to a request your site answered differently than you expected. This page covers the common ones: an ownership check that misses your proof, a firewall or bot challenge, and a site that SiteCMD says is down.

An ownership check misses your proof

When you check your proof from the site's setup page, SiteCMD reads the one place you chose and says what it found there:

  • The record is not there yet. SiteCMD looked up _sitecmd.example.com and found no TXT record holding this site's challenge. A new record can take a while to appear, depending on your provider. Some DNS providers add your domain to the name for you; if yours does, enter only _sitecmd.
  • The file is not there yet. SiteCMD asked for https://example.com/.well-known/sitecmd-site-verification and did not get this site's challenge back. SiteCMD reads the file without following redirects, so it has to answer at exactly that address, as a plain text file with the challenge on a line of its own.
  • The tag is not there yet. SiteCMD read the head of https://example.com/ and found no sitecmd-site-verification tag holding this site's challenge. SiteCMD reads the page as your server sends it, so a tag a script adds, or one in the page's body, does not count.
  • SiteCMD could not read the record, the file or the meta tag. The site refused or challenged the check. Prove ownership by DNS, which no firewall or bot challenge affects.

Check that the name and the value match what the setup page shows, then check again. If your site's address sends visitors to another host, prove it with the DNS record: its pages redirect, so the file and the meta tag cannot be read there.

After the site is proved

SiteCMD checks it every 24 hours and emails you if a check misses it. If the checks keep missing it, the site goes back to being watched only for a limited time, until you prove it again.

Settings, then Ownership, shows when the last check ran and what it found: the site's challenge, nothing in any of the three places, or a reason it could not read them. A check your site refuses or challenges, or one that gets no answer or a server error, is not a miss. Checks that keep failing to read the proof still send the site back to being watched for a limited time, so if a firewall is in the way, move the proof to the DNS record.

If Ownership says another SiteCMD challenge is in the same place, it may be keeping another account's proof of your site standing. Remove the one that differs from your site's challenge and keep the one that matches.

A firewall or bot challenge answers SiteCMD

A firewall or bot protection can answer SiteCMD with a challenge page instead of your site. What happens depends on which request it stopped.

  • An ownership check. It is not read as a miss, as above. Prove ownership by DNS, which no firewall or bot challenge affects.
  • The uptime probe. The site counts as down, and SiteCMD's alert says Uptime check blocked by a firewall challenge. To let the probe through, allow the user agent SiteCMD-Probe/1 in your firewall; anyone can send that user agent, and no rule can let SiteCMD's probe past Cloudflare's Bot Fight Mode.
  • A scan. A page a challenge answered is listed in that scan's coverage with the reason "a bot challenge answered", and nothing the scan read on it counts, so it neither raises a finding nor clears one. A firewall rule can let scans through by their user agent, below, with the same caveat: anyone can send it.

SiteCMD's requests come from Cloudflare's network, and their source address depends on the location that sent them, so there is no address list to allow.

SiteCMD says the site is down

The uptime probe requests your home page every 5 minutes. It follows your redirects and counts the site as up only when the last answer is a success. No answer within 10 seconds, an error status such as 403 or 503, or a firewall challenge counts as down. A probe that disagrees with the site's last state is asked again 60 seconds later, and the state changes only when that answer agrees, so one slow answer does not send an alert.

If your site answers you but not SiteCMD, look for a rule that treats unknown visitors differently: a firewall, bot protection, rate limiting, or a rule that blocks requests from Cloudflare's network.

How SiteCMD's requests name themselves

Every request SiteCMD sends your site, apart from the webhooks you set up, carries one of three user agents:

  • Scans, and the read of your certificate: SiteCMD/{version} (+https://sitecmd.com/scanner), with {version} the scanner's release.
  • The uptime probe: SiteCMD-Probe/1 (+https://sitecmd.com/scanner).
  • The ownership checks, and the read of your home page when you add the site: SiteCMD-Verify/1 (+https://sitecmd.com/scanner).

A user agent is a label, not proof: any client can send it, so use it to read your logs and never as authentication. The certificate read loads your home page in a Cloudflare Browser Run session, which makes the connection itself, so that request also carries whatever Browser Run adds to its own requests.

SiteCMD reads your pages over HTTPS. Some of a scan's checks also send a request over plain http:// on port 80, such as the one that checks that http:// sends visitors on to https://. A few look hostile in a log, such as the open-redirect check, which asks for your pages with redirect parameters aimed at https://evil.example.com, a domain reserved for examples. The SiteCMD scanner lists every kind of request a scan sends, as it appears in a server's log.

If your first scan did not finish

The site's home then says Your first scan did not finish, and SiteCMD tries again on its schedule. Scans lists the attempt, and opening it shows each page it covered and the checks it could not speak for, with the reason. A page SiteCMD could not check, such as one a bot challenge answered, is listed there.

Still stuck

Write to SiteCMD from the Contact page, and say which site and what SiteCMD showed you, in its own words.