The recorder says why it could not start
When a site’s own security settings block recording, the visitor is told plainly that it is the site and not their device. The exact fix goes to the browser console, for whoever installed the widget.
Two different blocks used to end in the same dead end telling the visitor to contact support: a security policy on the page that does not allow our realtime connection, and a page header that switches the microphone off for everything on it. The widget now tells those apart, because a browser reports them differently even though the error looks identical, and names the exact entry to add for each one.
A widget installed on an address that does not match its settings now says so in the console instead of quietly not appearing, and the recording library no longer narrates its retries into your visitors’ consoles. The Recording Sources card on a widget also stopped vanishing when it had nothing to list, and now says whether the widget has never been used or its recordings have passed your storage period.
