Section
Troubleshooting
The exact error, the real cause, and the fix that works.
4 articles
- The deploy fails with a Cloudflare API error Fix a failing Hatch deploy to Cloudflare: missing token permissions, expired token, a rejected frontend account, or a site Cloudflare cannot reach.
- The REST API returns 404, and the permalinks fix Fix a 404 on /wp-json/hatch/v1 or the WordPress REST API by switching from plain permalinks to a pretty permalink structure, and what else to check.
- Hatch Application Password or Login Fails Fix Hatch deploys that reject the frontend account or Application Password, and frontend sign-ins that fail, using the rules Hatch actually enforces.
- Site Shows Old Content After Publishing Hatch frontend still shows old content after you publish? Check the refresh signal, the post type, the webhook secret and WP-Cron, then refresh by hand.
Other sections
9
Getting Started
Install it, connect Cloudflare, deploy, and confirm it is actually running.
All getting started
24
Features
Every Hatch feature explained, one page each, with what it does and does not do.
All features