Use this page when a domain connected through your own platform (Integration Mode) doesn't connect, stops syncing, or a redirect doesn't fire. Open the domain under Hostnames first: its status and the result of the last check tell you where to start.
Status: Waiting#
Waiting means RedirHub hasn't received a correct answer from the check path on your domain yet. Open https://your-domain/_redirhub/check in a browser. It should return a short line of plain text that starts with token=.
- 404 or your own page: the integration isn't running on that hostname yet. Check that it's deployed, that it runs on this exact hostname (www and the root domain are separate), and that your routes let
/_redirhub/checkthrough. - Next.js: the middleware or proxy matcher must include
/_redirhub/check. - Cloudflare Workers: the Worker route must cover the hostname, for example
shop.example.com/*. - A different token: the integration uses the rules address of another domain or workspace. Copy the rules address again from the dashboard.
- Nothing at all (timeout, error page): the integration hasn't downloaded its first rules file yet. Until it has one, it doesn't answer the check path. Check the rules address in its settings.
Status: Sync stopped#
Sync stopped means your platform answers the check path but no longer runs the latest rules: its rules are older than the ones RedirHub published. RedirHub also sends you an email when this happens.
- Check that the integration can still reach the rules address (a firewall, a changed environment variable or an expired deployment are the usual causes).
- Redeploy or restart the integration after changing its settings.
If a domain stays out of sync for 7 days, RedirHub deactivates it. Fix the integration and the domain connects again at the next check.
A redirect doesn't fire#
- Wait a minute. The integration downloads new rules about once a minute (Caddy can update within seconds).
- Test in a private window or with curl -I. Browsers remember 301 redirects, so your own browser may show the old result.
- Your site answers first. A catch-all rule only answers URLs your site returns 404 for. If the page exists, your site wins. Use an exact rule for that path instead.
- Next.js: call the redirects first in your proxy, before rewrites and locale handling. A matcher that skips every path with a dot also skips rules such as
/old.html. Redirects in next.config run before the proxy and can shadow your rules. Next.js doesn't serve catch-all rules, because the proxy never sees your site's final status. - Not applied in Integration Mode: Custom HTML, frame redirects, password protection, paused or expired links and wildcard domains. A link with several destinations uses its main destination.
Visits or 404s don't show in analytics#
- Reports are sent with your workspace's integration key. Check that the key is set in the integration (as a secret or environment variable) and that it's the current one.
- 404 reports are sent only when 404 reporting is on for the domain (it is by default) and the platform supports it.
- Reports are sent in the background in small batches, so allow a minute or two before checking.
Still stuck?#
Send us the domain, your platform and what https://your-domain/_redirhub/check returns. We'll check the integration from our side.
Frequently asked questions
RedirHub hasn't received a correct answer from the check path on your domain yet. Usually the integration isn't deployed yet, or it doesn't run on that hostname or on /_redirhub/check.
The integration downloads the rules about once a minute (Caddy can update within seconds). Browsers also remember 301 redirects: test in a private window or with curl -I.
A common middleware matcher skips every path with a dot, so rules like /old.html never reach the proxy. Redirects in next.config also run first and can shadow your rules.