If your Kerabie chat bubble isn't showing up, work through this checklist in order. Most issues are resolved in the first two steps.
1. Confirm the script is installed
Open your browser's DevTools (F12) and go to the Network tab. Reload the page and search for widget.js. If you don't see it loading, the script hasn't been placed correctly.
Fix: Paste the script just before the closing
tag in your HTML. For WordPress users, use the Kerabie plugin instead of placing the script manually.
2. Check widget status
The widget can be toggled on or off from your dashboard.
1.Go to Settings → Widget.
2.Make sure Widget status is set to Active (green toggle).
3. Check allowed domains
If you've configured domain restrictions, your website domain must be in the allowlist.
1.Go to Settings → Widget → Allowed Domains.
2.Confirm your domain is listed. Add it if missing. Include both www and non-www versions if you use both.
Note: Localhost and staging domains (e.g., staging.mysite.com) need to be added separately if you're testing there.
4. Check for ad blockers or privacy extensions
Browser extensions like uBlock Origin, AdBlock Plus, or Privacy Badger sometimes block chat widgets.
Fix: Test in a private/incognito window with extensions disabled. If the widget appears there but not normally, an extension is the cause.
5. Check browser console for errors
Open DevTools → Console tab. Look for any red error messages containing "kerabie" or "widget".
Common errors and fixes:
•Invalid Widget Key — copy the Widget Key again from Settings → Widget → Install Code.
•CORS error — your domain may not be in the allowed domains list.
•Script blocked by CSP — add widget.kerabie.com to your Content Security Policy.
6. Check your Content Security Policy (CSP)
If your site uses a strict CSP header, the widget script may be blocked. Add these to your CSP:
If you just installed the script, your CDN or browser may be serving a cached version of your page without the script.
Fix:
•Clear your browser cache (Ctrl+Shift+R or Cmd+Shift+R).
•If you use a CDN (Cloudflare, Vercel, etc.), purge the cache for the affected pages.
8. Single Page Apps (SPAs)
If your site is a React, Vue, or Angular SPA, the widget script must be placed in the root HTML file (e.g., index.html), not inside a component. The widget initialises once per page load, not per route change.
Still not showing up?
Contact our support team through the dashboard. Please include:
•Your website URL
•Browser and version
•A screenshot of the browser console errors (if any)