Strict Content-Security-Policy headers can block third-party widgets even when the script tag is in HTML. The console usually names the blocked URL.
Fix CSP
- Open the live page, open browser DevTools, and read Console for CSP violation messages
- Note which directive blocked getamevia.com or the widget script URL
- Update script-src to include the Amevia script host shown in Installation
- Add connect-src entries if fetch or WebSocket calls to Amevia are blocked
- Publish the header change (server, meta tag or CDN transform)
- Hard-refresh and run Recheck installation
Common setups
- Report-only CSP logs violations without blocking — switch to enforce mode only after testing
- WordPress security plugins add CSP — update the plugin allowlist, not only .htaccess
- See CSP and script blocking for ad blockers and extension tests