Docs · Reference
Troubleshooting
The Pro registry errors, with the exact message you see and how to fix them, plus the most common problems when using the components.
On this page
Pro registry errors
When something fails, the registry responds with an HTTP status and a JSON body with two fields: error, a short code, and message, the explanation in English. The shadcn CLI shows you the message.
{
"error": "licencia_desconocida",
"message": "We couldn't find that license. Check it at https://furin.dev/license/ or email contacto@furin.dev."
}401: your license wasn't accepted
licencia_requeridaYour Furin Pro license is missing. Send it in the header "Authorization: Bearer FURIN-XXXX-XXXX-XXXX-XXXX" (in components.json use "Bearer ${FURIN_LICENCIA}" and define FURIN_LICENCIA in your .env.local). Don't have one yet? https://furin.dev/pricing/
What to do. The registry didn't receive the license. Check that components.json has the headers block (see how) and that FURIN_LICENCIA is defined in the same environment where you run the CLI.
licencia_con_formato_invalidoThe license isn't in the right format (FURIN-XXXX-XXXX-XXXX-XXXX). Check that FURIN_LICENCIA is defined, complete, and has no quotes or extra spaces. You can verify your license at https://furin.dev/license/
What to do. Copy the license again, in full, from your purchase confirmation page or from Use my license. In the .env file it goes without quotes.
licencia_desconocidaWe couldn't find that license. Check it at https://furin.dev/license/ or email contacto@furin.dev.
What to do. Paste it into Use my license: that's where it gets verified. One character too many or too few is enough for it not to exist; remember it has no zero, no letter O, no one and no letter I.
licencia_de_otro_entornoThat license belongs to another payments environment (test or live) and doesn't work here. Use the license from your real purchase or email contacto@furin.dev.
What to do. A license from a test purchase doesn't work on the live site, and the other way around. Use the one from your real purchase or email us at contacto@furin.dev.
licencia_reembolsadaThat license was refunded and is no longer active. If you think this is a mistake, email contacto@furin.dev.
What to do. A refund deactivates the license. If you didn't ask for a refund, email us at contacto@furin.dev.
403: it's not in your plan
fuera_de_tu_plan"<component>" was released after your purchase (<your purchase date>). Your Pro license includes the components that existed that day; with Lifetime you get the whole catalog, including what's new: https://furin.dev/pricing/
What to do. The component was released after your purchase and your plan is Pro. With Lifetime you would have the whole catalog (see the difference). The other components keep working.
404: that name doesn't exist
no_es_pro"<name>" is not a Furin Pro component. Available with your license: <list of names>.
What to do. Check the component name: it's the one on its catalog page (/components/<name>/). Free components aren't installed with @furin-pro but with their public URL (see Installation).
ruta_desconocidaThat route doesn't exist. The Pro registry is at /api/pro/r/{name}.json.
What to do. Check the registry url in components.json: it must be https://furin.dev/api/pro/r/{name}.json.
429: too many requests
demasiadas_peticionesToo many requests from your connection. Try again in N seconds.
This license made too many requests in the last hour. Try again in N minutes.
This license made too many downloads in the last hour. Try again in N minutes.
This license was used from too many different connections today (maximum 8 per day): licenses are personal. It will work again tomorrow; if this is a mistake, email contacto@furin.dev.
What to do. Wait as long as the message says (it also comes in the Retry-After header, in seconds) and don't retry in a loop. How much each cap allows is in Usage limits.
Other errors
metodo_no_permitidoUse GET.
What to do. The registry and the download only accept GET; verifying a license, only POST. If you use the shadcn CLI you shouldn't see this.
error_internoSomething went wrong on our side. Try again in a moment.
What to do. It's not your license or your setup. Wait a moment and try again; if it keeps happening, email contacto@furin.dev.
When installing or importing
Cannot find module furin-ui/<name>
The furin-ui/<name> paths only exist for the 92 free components, and the name is the one on its catalog page. Pro components aren't in the package: they install with your license (Furin Pro).
TypeScript can't find the types for furin-ui/<name>
The package declares its paths with exports. For TypeScript to read them, your tsconfig.json needs "moduleResolution": "bundler" (or "node16" / "nodenext"). Next.js and Vite already include it in their templates.
When it looks wrong
The component shows up without styles
Components import their CSS, so your bundler must be able to import .css files. If yours can't do it from node_modules, import the full stylesheet once (import "furin-ui/estilos.css") or install with shadcn, which leaves the CSS in your project.
The background covers the whole page, or doesn't show
Backgrounds fill their container. Give the container position: relative and a height; without a height, the background is zero tall (see the example).
It doesn't move
Check whether your system has reduced motion turned on: components respect it and stay still (see how to test it). They also pause when they leave the screen or when the tab isn't in view.
A WebGL background goes blank
There may be too many live WebGL contexts on the page: the browser shuts down the oldest ones. Keep only a few at a time (see Performance). If it only happens on one machine, check that the browser has graphics acceleration turned on.
In Next.js
Functions cannot be passed directly to Client Components
A Server Component can't pass a function to a client component. If you pass a callback (such as onRing), use it from a file with "use client" (see the example).
If none of this helps
Email us at contacto@furin.dev. Tell us which component you're using, your framework and your React version, and paste the full error message. Don't paste your full license in the email.
Spot a mistake or something missing? Email us at contacto@furin.dev.