Troubleshooting

Cabina never breaks your storefront: when it cannot work, it removes itself. That is deliberate, and it is also why some of these failures are completely silent.

No button anywhere on the product page

In the console: a CORS error from your browser, naming www.cabina.io

Your store domain is not on the authorised list, so the API answers without CORS headers and the browser drops the response.

Add the exact origin at Widget . https://shop.com and https://www.shop.com are two different origins: add both if both serve the store.

The same list applies to try-ons: a try-on requested from a site that is not on it is refused (403) before any credit is used. If try-ons stopped after a domain change, the fix is the same: add the new domain.

No button, and no CORS error either

In the console: [widget] error=WIDGET_CONFIG_MISSING

The API key is missing, or it was not read from the script tag.

Check that data-api-key sits on the <script> tag itself and starts with cab_live_.

No button, nothing in the console at all

In the console: nothing — this one is silent

Your plan has run out of sessions, or your credits are exhausted. The widget hides itself on purpose, so your store keeps working.

Check Billing .

The button sits at the very bottom of the page

In the console: nothing — this one is silent too

None of the known anchors matched your theme, so the button was appended to <body>.

Add <div data-cabina-target></div> where you want it: the button goes inside that element. See Moving the button.

Two buttons, and sessions counted twice

In the console: [widget] warn=GIA_CARICATO

The snippet is on the page twice — often an old copy plus a plugin.

Remove one of the two <script> tags.

The button opens, but the try-on fails partway

In the console: nothing

Cabina could not find the garment image on the page.

Add an og:image meta tag to your product template — see The garment image.

Some try-ons fail when many shoppers try at once

In the console: nothing; in the browser’s Network tab, a 429 response

Cabina accepts at most 30 try-ons per minute per store, so nobody can drain your credits in a few minutes with the public key. Above that threshold the try-on fails: trying again shortly is enough.

The try-on starts, then fails with “Try-on failed”

In the console: nothing

The widget found the garment and the customer’s photo, but the generation did not finish. A failed try-on does not use credits. The reasons, from the most common to the rarest:

• The garment photo is not usable. A collage, a close-up, a garment seen from the back or with text over it is not enough for the engine. The right photo is described in Photos.
• The customer’s photo. Full figure, standing, well lit: it is advice, not a rule, but a person cut in half or several people in the same photo make the generation fail.
• The engine is temporarily down. It is rare; the live status is on cabina.io/status . Trying again a few minutes later is enough.

If the month’s try-ons are used up instead, the button disappears from the product pages until the plan renews or you buy extra try-ons from Plan .

Lingerie, swimwear and see-through garments

In the console: nothing

The AI models Cabina uses to recognise the garment and to generate the try-on belong to outside providers, and they apply content rules that do not depend on us. Lingerie, swimwear and sheer fabrics can be rejected by those rules: garment recognition may fail, and the try-on may not start or may stop halfway.

We tested lingerie (October 2026: lace and mesh sets, sheer bodysuits, garter sets, pyjamas and nightgowns, on four body types): the try-on came out for every garment. Garment recognition rejected only one photo, where the garment was worn by a model; when that happens, the try-on still starts. For lingerie, a photo of the garment on its own matters even more.

We have not tested swimwear or see-through garments that are not lingerie (blouses, dresses) yet: if you sell them, write to us with a product link before enabling Cabina and we will test it together.

The button works, but no size is suggested

In the console: nothing

The shopper has not given the measurements that garment needs — for example only their height on a top, which needs bust and waist. The widget would rather show no size than guess one.

The measurements each kind of garment needs are in The dashboard.

Verifying from a terminal

# 1. the tag is actually served
curl -s https://your-store.com/products/some-product | grep -o 'widget.iife.js'
 
# 2. the page exposes a garment image
curl -s https://your-store.com/products/some-product | grep -o 'og:image[^>]*'

These are the two that fail. If both answer, the problem is almost always the unauthorised domain.

None of these cases?

Write to info@cabina.io with a link to a product page and, if you can, what you see in the console.