Help Center

Connection refused" problem with Embed Pages and Webviews

If you read the message "... connection refused":

undefined

When you insert an Embed Page or Webview add-on into your website, here's why it happens and how to set it up: 

First distinguish between 2 scenarios:

1. URL of the domain itself

For example, if we have the bot inside our website: "https://www.aivo.co/", and we enter the URL "https://www.aivo.co/conversational-ai" inside the add-on, it will work correctly.

2. URL of another domain

Continuing with the example in point 1), if a URL from another domain is entered into the add-on, https://aivovideos.co/example1 functioning will depend on the configuration of this site.

  1. Now, focusing on scenario 2, a common problem is that youtube videos don't work. We explain how to make it work.
  2. Incorrect way to configure the youtube video:

undefined

Forma correta de configurar o vídeo de Youtube:

undefined

The result of both cases can be seen in this video:

https://drive.google.com/file/d/1itAdnBPJ24h8tU_WomFsDxoLR7G3z6xW/view?usp=sharing

Finally, if you need to enter a URL that you own but which is on a different domain than the site on which the bot is located, here are some possible solutions that will depend on the characteristics of your sites.

You may need support from your technical team.

The main problem comes from the HTTP X-Frame-Options response header that can be used to indicate whether a browser should be allowed to render a page in a <frame> <iframe> or <object>. 

Available settings:

DENY: The page cannot be displayed in a frame, regardless of which site is trying to display it.

SAMEORIGIN: The page can only be displayed in a frame with the same origin as the page.

ALLOW-FROM uri: The page can only be displayed in a frame with the specified source.

To solve this problem, you can use one of the following options, adding to the site you want to insert or adding to the iframe.

Apache Configuration

Add the following to your site configuration so that Apache sends the X-Frame-Options header to all pages:

Header always append X-Frame-Options SAMEORIGIN

To have Apache send the X-Frame-Options header to ALLOW-FROM a specific host, add this to your site configuration:

Header set X-Frame-Options "ALLOW-FROM https://example.com/"

nginx configuration

To configure nginx to send the X-Frame-Options header, add this to the configuration, either http, server, or location:

 add_header X-Frame-Options SAMEORIGIN;

ISS Configuration

For IIS to send the X-Frame-Options header, add this to your site's Web.config file:

<system.webServer>

  <httpProtocol>

    <customHeaders>

      <add name="X-Frame-Options" value="SAMEORIGIN" />

    </customHeaders>

  </httpProtocol>

</system.webServer>

HAProxy Configuration

To have HAProxy send the X-Frame-Options header, add the following to your frontend, listen, or backend configuration:

rspadd X-Frame-Options:\ SAMEORIGIN

This website stores cookies on your computer. These cookies are used to collect information about how you interact with our website and allow us to remember you. We use this information in order to improve and customize your browsing experience and for analytics and metrics about our visitors both on this website and other media. To find out more about the cookies we use, see our Privacy Policy.

If you decline, your information won’t be tracked when you visit this website. A single cookie will be used in your browser to remember your preference not to be tracked.