TOPIC:

Club: 4260

Hi there,

I created a link to our District's website (iFrame - see link below) which was working fine until a day or so ago. Iframes on Home page are working fine. I read the Admin notes from Steve regarding adding <https> instead of just <http> but that results in an error message. I'm not sure how to fix this. Thank you in advance for your assistance.

humbershorestoastmasters.toastmastersclubs.org/District_60.html

Mamta, VPPR

You can certainly try to use a protocol relative url ... "//" without the http: or https:, but there are no guarantees.

The fundamental issue is that your district website referenced in your iframe is not supporting https (not secure--I tried it)... you should mention something to them about that. Tell them that Comodo and Let's Encrypt offer free SSL certificates (for HTTPS) for non-profits.

I am probably going to undo the redirect that is forcing FTH websites using the toastmastersclubs.org domain to HTTPS. Of course, all that would does is force you to use http: (not secure) to see the district website in the iframe. You would have to degrade your overall website security to see the insecure content.

I will also look at a middle ground approach to try to make the insecure content be included despite the issues (for now), but this approach looks like it is going to need some additional code created. (takes time)

I wish I had a better solution for you, but again this is related to the content that you are referencing not being secure via https.

This is a good example of why I suspected moving to HTTPS was not going to be as easy as some users were suggesting.

Ok, I have disabled the redirect to HTTPS again ... temporarily, to give websites like yours time to deal with insecure content.

Instead of iframe the site just link to the district site.

Thank you. It works again.

Also, In case no one has brought up this issue, and perhaps it's related but when logging in to the Website - as Administrator or regular member - I get a message saying that site is not secure. Oddly enough it started after we were switched to HTTPS?

Thank you again!

SteveTheTechie wrote:

Ok, I have disabled the redirect to HTTPS again ... temporarily, to give websites like yours time to deal with insecure content.

The insecure message comes from your browser. My guess is that you're using Firefox. They started doing this with version 52.

mamta wrote:

Thank you. It works again.

Also, In case no one has brought up this issue, and perhaps it's related but when logging in to the Website - as Administrator or regular member - I get a message saying that site is not secure. Oddly enough it started after we were switched to HTTPS?

Thank you again!

SteveTheTechie wrote:

Ok, I have disabled the redirect to HTTPS again ... temporarily, to give websites like yours time to deal with insecure content.

Ok, you cannot have it both ways.

You either need to stop including insecure content if you intend to use https: (which will get rid of the FireFox warning) or you need just use http: and put up with the warning.

Although the security warning is coming from FireFox when using http:, this is a mixed content issue with your content--you need to fix your content if you wish to use https:.

Hi Steve,

thank you for your help and sorry for the misunderstanding. I'm the furthest thing from a techie so all of this is like gobbledy-gook lingo to me. I fell into the Admin role and have used trial and error etc. to learn how to do even basic updates on our website. IFrame is my proudest accomplishment so far lol

So, clarify about mixed content, I'm not trying to do both things - I just didn't understand the connection although I've learned quite a bit about http vs https from reading through this forum.

Thank you again to everyone who provides support to us non-techie types. I imagine it's not easy Cheers!

You are not alone in this... sorry if I was a bit hard on you... I am getting bit frustrated because I cannot figure out how to make some of this stuff any simpler, but I would like to.

The catch is when you switch to https, browsers generally expect just about everything in your website to use secure access. They will complain about or take measures about some things more than other things, but generally if you have any insecure content when using https for your website, you can expect some problems.

If you district website cannot be accessed using https you will need to drop the iframe and just link to the District webpage you are including in the iframe. Not exactly what you want to do. When you district website can be accessed using https then you can add the iframe again.