Fixing the “Webvizio Was Blocked by the Website” Error

If you see this error and your site doesn’t appear in the background in Webvizio, your website’s security headers are most likely blocking it. Webvizio shows your site inside a frame, and two HTTP headers can prevent that: X-Frame-Options and Content-Security-Policy: frame-ancestors

X-Frame-Options header

X-Frame-Options stops your site from being displayed inside a frame on other websites, including Webvizio. Many hosting providers turn it on by default, and it can usually be turned off in your hosting settings.

How to fix it: remove the X-Frame-Options header.

• If you manage your own hosting, look for it in your hosting control panel, server configuration (for example, .htaccess or Nginx config), a security plugin, or your CDN settings.
• If you’re not sure where it’s set, contact your hosting provider’s support, or contact Webvizio support and tell us who your hosting provider is. We’ll help you find the right documentation to remove the header.

Learn more about X-Frame-Options on MDN.

🔒

Want to keep your site protected? If someone on your team is comfortable with server settings, replace X-Frame-Options with the Content-Security-Policy frame-ancestors directive described below. It blocks other websites from framing your site but still allows Webvizio.

Content-Security-Policy: frame-ancestors header

Hosting providers rarely set this header by default. It’s usually added by a developer or a security plugin. To allow Webvizio, add https://app.webvizio.com to the list of allowed sources in frame-ancestors:

Content-Security-Policy: frame-ancestors 'self' https://app.webvizio.com;

With this setting, your site can be framed only by your own domain and by Webvizio.

A few things to keep in mind:

• If your site already has a Content-Security-Policy header, add https://app.webvizio.com to its existing frame-ancestors directive instead of adding a second header.
• If you’re replacing X-Frame-Options, remove it entirely so the two headers don’t conflict.

Learn more about frame-ancestors on MDN.

Still seeing the error?

After changing the headers, clear your site’s cache and CDN cache, then reload the project in Webvizio. If your site now appears but you see “Script Not Detected,” see the article “Fixing the ‘Script Not Detected’ Error.”

If your site is behind a firewall or a service like Cloudflare, see the article “Fixing Website Display and Loading Issues.”

If the problem continues, contact us at support@webvizio.com or through the support chat. Include your project URL and the name of your hosting provider.