KINSTA_CACHE_ZONE setting Kinsta provides.
Kinsta runs nginx for you, and you can’t edit its configuration yourself. Kinsta also routes traffic through its own edge network. Server rules and edge settings on this page are changes to request from Kinsta support.
Start with the checks
In MainWP > AI > MainWP MCP > Connect directly, click Run the self-test, then Check from the internet. Note everyfail and warn line. Troubleshooting explains each one.
What to look at
The well-known addresses. nginx configurations often deny paths that start with a dot. If the self-test reports “Requests for the well-known addresses don’t reach WordPress, so no app can find how to sign in.”, or a subdirectory line says a server rule blocks addresses starting with a dot, send Kinsta support the rule from the nginx rules section with your path filled in. Bot protection at the edge. If the check from the internet reports “Something in front of WordPress blocks the well-known address: an error page, a server error or a challenge page.”, the edge network is answering the app’s request instead of WordPress. Ask support to let requests to these paths through without a challenge:/mainwp-oauth/ from the page cache and the edge cache.
What to send to support
- your Dashboard’s address
- the failing lines from the self-test and the check from the internet, word for word
- the rule the self-test shows, if any
- the time you ran the checks
rest_route points into /mainwp-remote/ and requests with a mainwp_oauth parameter in any relevant challenge or cache exception. Keep the exception specific to these endpoints.