If your website is showing as broken in BlueConic, this may be the result of changes to Chrome version 48 or 49 and how these versions changed handling http resources.
As of April 14th, 2016, Chrome 50 is released which fixes this issue.
Open the "About Chrome" menu and make sure you are using the latest version.
What happens is the following:
- BlueConic itself is loaded from a secure https address.
- When BlueConic tries to display your non-secure http website in a dialogue, in the simulator or in a visual picker, a warning will appear:
- Chrome allows you to click the shield icon as explained in the warning message. Previous versions of Chrome would then load your website just fine.
- However, in Chrome version 48 clicking the icon only allows the browser to load the non-secure webpage itself. The same courtesy isn't extended to non-secure http resources that the webpage wants to load, like style sheets, scripts and images. The result is what looks like a broken page and a message that the BlueConic script cannot be loaded:
A bug report has been submitted to the Chrome development team and the issue has been classified as a bug that will be fixed in Chrome 50.
At the time of writing there was no solution for this problem, but there are a couple of workarounds possible:
- If possible, load your website from its secure https address. Avoid using non-secure http addresses.
- Use a different browser to work with BlueConic, for example Firefox.
Start Chrome with the --allow-running-insecure-content option. On Mac open a Terminal and enter the following command:
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome \ --allow-running-insecure-content
On Windows, click the right mouse button on the Chrome shortcut, select "Properties" and add the option to the end of the target so it ends in: ...\chrome.exe" --allow-running-insecure-content