## **☁️ What this article covers**

Some customers saw OTTO SEO reject a newly generated Cloudflare API token. Cloudflare’s own token instructions also did not match the screen they were looking at. Permission walkthroughs did not fix the connection. This article explains the confirmed cause and what to do now.

## **🛠️ What actually caused the failure**

Support confirmed that a migration of our hosting, from GitLab to Anvil self-hosted, affected the Cloudflare Worker that OTTO uses. The token itself was not the problem, and changing Cloudflare permissions did not resolve it. Engineering tracked the fix as an urgent platform issue: the Worker’s fetch behavior after that migration.

Engineering corrected the Worker’s fetch behavior after the hosting migration (OTTO-3842). Once that fix is live in production, a normal Cloudflare API token is enough and no special setup is required to work around the old failure. Until you have confirmed the fix is released, retrying with a new token may still fail for the same reason.

## **🚀 What you should do**

1. In your OTTO project, open the installation guide and select the DNS Setup tab. That is where you paste the Cloudflare API token.
2. Generate a Cloudflare API token as you normally would, paste it into the “Paste your API Token” field on the DNS Setup tab, and click “Validate & Connect.”
3. If OTTO accepts the token, no further action is required.

Do not treat an older permission checklist as the fix for the failure that started right after the hosting migration. That break was in the Worker fetch, and permission changes did not fix it. If a token is still rejected after the fix is live, check the token itself: it must be active, created in the Cloudflare account that holds the domain, have no Client IP Filtering, and include the Workers, Workers KV, DNS, and Worker routes permissions OTTO asks for.

## **💡 If the token is still rejected**

If OTTO still will not take a valid token after you try again, the remaining issue needs a support agent. Include when you last tried, that Cloudflare’s screens do not match the usual token instructions, and that you already retried after the Worker fix.

If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.