-
AuthorPosts
-
November 24, 2017 at 6:32 am #881073
Hi team! I hope you’ve all been well :)
We migrated recently to https and all is working well except for one weird issue. 99% of the time the site loads fine but every few days we are surprised with a stylesheet being blocked due to it being mixed content. It looks to be enfold.css that is getting called over http for some reason?
The weird things are that:
a) this only gets called mixed content every few days for some reason, please see two screenshot urls in the private area. The first is how the site usually loads, and the second is the rare instance enfold.css loads as mixed content and then causes the issue. Any idea why this is only happening occasionally?
b) the url in our page source for enfold.css is https, so not sure why it’s being called mixed content by the browser.Thank you as usual for your time on this!
Best,
JonathanNovember 24, 2017 at 4:14 pm #881267Hey Jonathan,
Can you give us temporary admin access to your website in the private content box below, so that we can have a closer look?
Best regards,
VictoriaNovember 24, 2017 at 6:54 pm #881365Hi Victoria,
There is a chance this is an issue with how my cdn provider is pulling from the theme, as I’ve excluded .css and .js from the cdn and that (at least for now) fixed the issue. I’ll keep an eye on it and will let you know if it re-occurs. I will also update with the findings by my cdn provider.
Do you have any reason to believe there is an issue with how enfold works with https and/or cdn setups though that could be causing this? Any reason .js and .css may be called sometime as unsecure content?
My install is just a regular enfold install, only css changes with custom.css, but nothing else. So perhaps you can inspect on your install first before needing to go into mine. It is a live business website so I prefer not to give out access unless/until necessary. Thank you for understanding. Please let me know, thanks!
Thank you for your time.
Best,
JonathanNovember 25, 2017 at 2:51 pm #881619Hi Jonathan,
Thank you for sharing! Some cdn providers do that, and maybe you have http before and moved to https and the cdn has some long-term cache and so the script links did not update, even though it’s very unlikely.
Glad you got it working for you! :)
If you need further assistance please let us know.
Best regards,
VictoriaNovember 27, 2017 at 2:04 am #882067Hi Victoria,
I’ll keep you posted but even if it is the cdn it may be the way it’s pulling the theme files. As far as I can tell there are no http links in my database.
Do you have any reason to believe there is an issue with how enfold works with https and/or cdn setups though that could be causing this? Any reason .js and .css may be called sometimes as non-secure content?
It would be ideal to be able to re-enable css and js files to the cdn.
Thank you,
JonathanNovember 27, 2017 at 11:09 pm #882391Hi,
CDN should not bring issues, but the point is that you need to know what stuff you send over to the CDN.
For a better configuration is better to contact a devoper to hire them help you on how to manage things.Thank you
Best regards,
BasilisNovember 27, 2017 at 11:23 pm #882397Thank you Basilis,
Please keep this open as I will be in touch if I narrow the issue down. For the time being though everything seems fine as long as we exclude .css and .js from the cdn for some reason. I’m not sure why this is.
I’ll be in touch if needed, and either way I will update this in the future if resolved.
Many thanks,
JonathanNovember 27, 2017 at 11:28 pm #882401Hi Jonathan,
We will keep the thread open and wait to hear from you. Thread will be on hold until you reply :)
Regards,
YigitNovember 27, 2017 at 11:35 pm #882405Perfect, thank you!
-
AuthorPosts
- You must be logged in to reply to this topic.