Tesla Pro - SSL Site but unsecure content

I just created a Tesla Pro site which is secured with a SSL certificate.
However when loading the page, the browsers (Opera, Firefox, Safari) tell me that they have blocked unsecure content.
I did some investigation and identified the following link address to be unsecure “http://netdna.bootstrapcdn.com/font-awesome/4.2.0/css/font-awesome.min.css

In addition Opera gives me the following explanation:
“Mixed Content: The page at ‘https://’ was loaded over HTTPS, but requested an insecure stylesheet ‘http://netdna.bootstrapcdn.com/font-awesome/4.2.0/css/font-awesome.min.css’. This request has been blocked; the content must be served over HTTPS.”

Can this be changed within Tesla Pro or is it even a bug? Because dependend on browser settings the user experience will be disturbed by the browser’s warning messages.

I bet, this might be an issue with Foundry, too…

Thanks in advance
Regards Thomas

Hi there Thomas – The Tesla Pro theme does not use Bootstrap or its CDN anywhere. Perhaps you’re using something else on the page that is loading this CDN? If you’d like to send me a ZIP file containing your project file and any non-Elixir stacks you might be using, I’d be glad to take a look.

Tesla Pro references no files outside of itself (like the CDN you’re referring to above) and in fact it uses an old version of Zurb’s framework for its columnized layouts, etc.

As for Foundry – this is not a problem with Foundry either, as Foundry includes its own, custom version of Bootstrap internally, and not through a CDN. In fact Foundry’s Bootstrap is generated internally via SCSS when the page is either rendered in Preview Mode or when it is Exported or Published with RapidWeaver.

1 Like

Thanks, Adam, for the explanation.
I reviewed my site and did some testing. As I am using uweather stack and formsnap pro besides the Tesla Pro theme, I discovered the formsnap stack to be the one trying to load unsecure contend.

Again thanks for your support, I will get in touch with yabdab to clarify this issue (of course I will post the results here).


Hi Adam,

could it be that your Ivy2 stack tries to load that Bootstrap font?
On my site I am using formsnap and within formsnap Ivy2.
Mike from yabdab told me that they do load Font Awesome resources locally only.

Thanks and Kind Regards

Ivy does not load an external version of Font Awesome. It tells the Stacks plugin to load it and then uses whatever settings you have in Stacks for loading from CDNs:


Once GDPR launched I transitioned every currently maintained stack and theme over to using non-CDN based resources.

Hi Adam,
thanks again for the information.
However, I did even more testing… Please see the small sample project attached.
As soon as you add the Ivy2 stack, in the “Plugin injected code” section of the source code you will find the http reference “”. When you are going to remove the Ivy stack, that reference will go away, too.
In any case the selection of the Stacks Preference panel does not have any effect on that behaviour.

My current workaround is to edit the index.php file after having published the project and change the link reference manually to https://… Maybe it will be worth to have a look into Ivy2 for you?

Thanks and Kind Regards

IvyTest.zip (24.7 KB)

Are you sure you’re using Ivy 2 and not the original Ivy stack? The original Ivy stack would have that problem as it was not updated for GDPR because it had long been retired and replaced by Ivy 2 by that time. Please double check for me that you’re definitely using Ivy 2, and not just the original Ivy stack.

By the way, the reason I’m asking you do to this @TomS2 is because when I open your project file I see this:

The reason it says it is missing is because I have uninstalled Ivy v1 on my computer and only have Ivy v2 installed. This indicates to me that you’re using Ivy v1.

If you were using Ivy v2 you’d see this as the outer wrapper of the stack:

1 Like

You got it :wink:

Sorry for misleading… I am, in deed, using V1… unbelievable.
How to upgrade? Just buying the new version?


That are totally different stacks. The whole underlying code base is different. It is just a matter of buying v2 and redoing your accordion layouts with the new version.

Thanks Adam,

I will do so. Keep up your excellent work - I simply love your products.

Kind Regards Thomas

1 Like