Troubleshooting

Ad blockers prevent feedback submission

Browser extensions like uBlock Origin, AdBlock Plus, or Brave Shields may block requests from the Feedboon widget to api.feedboon.com. When this happens, feedback submissions fail silently.

How to tell

Open the browser's developer console (F12 → Console tab). If you see errors like:

The ERR_BLOCKED_BY_CLIENT error confirms an extension is blocking the request.

Quick fix

Disable the ad blocker for the site where the widget is installed, or add it to the extension's allowlist. In most extensions you can click the icon in the toolbar and toggle it off for the current site.

Recommended fix: proxy through your domain

To avoid ad blockers entirely, proxy Feedboon API requests through your own domain. This way the browser only sees requests to your domain, which no ad blocker will block.

location /_feedboon/ {
    proxy_pass https://api.feedboon.com/api/v1/;
    proxy_set_header Host api.feedboon.com;
    proxy_set_header X-Real-IP $remote_addr;
}

async rewrites() {
  return [
    {
      source: '/_feedboon/:path*',
      destination: 'https://api.feedboon.com/api/v1/:path*',
    },
  ];
}

{
  "rewrites": [
    {
      "source": "/_feedboon/:path*",
      "destination": "https://api.feedboon.com/api/v1/:path*"
    }
  ]
}

Then update the widget script tag to use your proxy:

<script
  src="https://cdn.feedboon.com/fw.js"
  data-wk="YOUR_WIDGET_KEY"
  data-api-url="https://yoursite.com/_feedboon"
  async
></script>

Widget does not appear on the page

If the bug button is not visible in the bottom-right corner, check the following:

• Script tag is present: Make sure the <script> tag is placed before the closing </body> tag with the correct data-wk attribute.
• Authentication: The widget only appears for authenticated team members by default. Use the “Start Testing” button from the dashboard, or enable public mode in project settings.
• Console errors: Open the browser console and look for errors related to the widget loading.

Feedback submitted but not on the dashboard

If the widget showed a success message but the feedback doesn't appear on the Kanban board:

• Refresh the dashboard: The Kanban board loads data on page load. Refresh to see newly submitted feedback.
• Check the correct project: Feedback appears under the project matching the widget key used on the site.
• Check the archive: If feedback was accidentally archived, look in the Archive tab on the project page.

Pins not visible on the page

Pins are page-specific — they only appear on the exact URL where the feedback was submitted. Additionally:

• Done/Closed feedback: Resolved pins are hidden by default. Only New, In Progress, and Review pins are shown.
• URL must match: Pins for /dashboard won't appear on /dashboard?tab=settings. Query parameters are included in the URL match.

Screenshots look incorrect

Screenshots are captured client-side using the browser's rendering engine. Some elements may not render perfectly:

• Cross-origin images: Images loaded from external domains without CORS headers may appear blank.
• CSS variables: The widget resolves CSS custom properties automatically, but deeply nested or dynamically set variables may occasionally not resolve.
• Iframes and canvas: Content inside iframes or canvas elements may not be captured due to browser security restrictions.

Still need help?

If none of the above resolves your issue, reach out to us at [email protected] with a description of the problem, your browser console output, and which browser you're using.

Related docs