Skip to main content
Console
Hanko Auth Component
CORS errors usually happen when your app URL isn’t correctly set up in Hanko Cloud. If you’re developing locally, make sure to add something like http://localhost:3000. For production, use your live URL. Follow this guide for a smooth Hanko Cloud setup.Also, double-check that your app’s API URL is correct — even a missing or extra character when copying it from the Hanko Console can trigger a CORS error.
Console
Hanko Auth Component
This error typically arises when the API URL has been incorrectly configured. Depending on your framework, you may need to prefix your URLs with PUBLIC, NEXT_PUBLIC, or another specific prefix. This prefixing ensures that these environment variables are exposed to the browser and can be accessed by your frontend.Here are some of the examples
.env
Next.js
NEXT_PUBLIC_HANKO_API_URL=https://f4****-4802-49ad-8e0b-3d3****ab32.hanko.io

Nuxt
NUXT_PUBLIC_HANKO_API_URL=https://f4****-4802-49ad-8e0b-3d3****ab32.hanko.io

SvelteKit
PUBLIC_HANKO_API_URL=https://f4****-4802-49ad-8e0b-3d3****ab32.hanko.io

React
REACT_APP_HANKO_API_URL=https://f4****-4802-49ad-8e0b-3d3****ab32.hanko.io
You might get "r" is read-only error after you deploy a CRA (Create React App). To fix it you’ll need to add @babel/core as a dependency in your project. You can do this by running the following command:
npm install @babel/core
Feel free to open a GitHub Issue or join our Discord Community. We’re here to help!