# HTTPS Focus Item not working on HTTP Pages **URL:** \ **Category:** Product Support\ **Created:** [October 18, 2016, 5:37am UTC](https://forum.mautic.org/t/https-focus-item-not-working-on-http-pages/6264 "2016-10-18T05:37:21Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![namankapur](https://avatars.discourse-cdn.com/v4/letter/n/5f8ce5/32.png) [@namankapur](https://forum.mautic.org/u/namankapur)\ **Post date:** [October 18, 2016, 5:37am UTC](https://forum.mautic.org/t/https-focus-item-not-working-on-http-pages/6264/1 "2016-10-18T05:37:21Z")
Mautic is on HTTPS and so is the focus item JS. When embedded on HTTP pages, keep getting the following error: Failed to load resource: the server responded with a status of 403 (Forbidden) Uncaught SecurityError: Blocked a frame with origin “[https://mauticinstance.com](https://mauticinstance.com)” from accessing a frame with origin “[http://www.xxxxxxx.com](http://www.xxxxxxx.com)”. The frame requesting access has a protocol of “https”, the frame being accessed has a protocol of “http”. Protocols must match. Need help urgently. Thanks in advance! ---
**Author:** ![namankapur](https://avatars.discourse-cdn.com/v4/letter/n/5f8ce5/32.png) [@namankapur](https://forum.mautic.org/u/namankapur)\ **Post date:** [October 18, 2016, 5:37am UTC](https://forum.mautic.org/t/https-focus-item-not-working-on-http-pages/6264/2 "2016-10-18T05:37:21Z")
Mautic is on HTTPS and so is the focus item JS. When embedded on HTTP pages, keep getting the following error: Failed to load resource: the server responded with a status of 403 (Forbidden) Uncaught SecurityError: Blocked a frame with origin “[https://mauticinstance.com](https://mauticinstance.com)” from accessing a frame with origin “[http://www.xxxxxxx.com](http://www.xxxxxxx.com)”. The frame requesting access has a protocol of “https”, the frame being accessed has a protocol of “http”. Protocols must match. Need help urgently. Thanks in advance! ---
**Author:** ![Elenchus](https://avatars.discourse-cdn.com/v4/letter/e/ccd318/32.png) [@Elenchus](https://forum.mautic.org/u/Elenchus)\ **Post date:** [October 18, 2016, 7:21am UTC](https://forum.mautic.org/t/https-focus-item-not-working-on-http-pages/6264/3 "2016-10-18T07:21:24Z")
Best solution would be to make all your pages https Second answer here is why: [http://stackoverflow.com/questions/3331548/allowing-http-iframe-to-call-javascript-on-https-parent-frame](http://stackoverflow.com/questions/3331548/allowing-http-iframe-to-call-javascript-on-https-parent-frame) ---
**Author:** ![namankapur](https://avatars.discourse-cdn.com/v4/letter/n/5f8ce5/32.png) [@namankapur](https://forum.mautic.org/u/namankapur)\ **Post date:** [October 18, 2016, 12:48pm UTC](https://forum.mautic.org/t/https-focus-item-not-working-on-http-pages/6264/4 "2016-10-18T12:48:16Z")
Thanks for writing back. Converting all the pages into https is not an ideal task for us right now. Secondly, my question is the page is http but the JS is https which is creating an issue. The link you shared is not exactly solving our problems. ---
**Author:** ![Elenchus](https://avatars.discourse-cdn.com/v4/letter/e/ccd318/32.png) [@Elenchus](https://forum.mautic.org/u/Elenchus)\ **Post date:** [October 20, 2016, 1:03am UTC](https://forum.mautic.org/t/https-focus-item-not-working-on-http-pages/6264/5 "2016-10-20T01:03:34Z")
This is the closest thing I’ve been able to find to your issue: [http://stackoverflow.com/questions/1105934/ajax-using-https-on-an-http-page](http://stackoverflow.com/questions/1105934/ajax-using-https-on-an-http-page) ---
**Author:** ![manageit](https://avatars.discourse-cdn.com/v4/letter/m/5daacb/32.png) [@manageit](https://forum.mautic.org/u/manageit)\ **Post date:** [October 23, 2016, 8:13pm UTC](https://forum.mautic.org/t/https-focus-item-not-working-on-http-pages/6264/6 "2016-10-23T20:13:01Z")
@namakapur I would “highly” recommend making the effort to fully switch to all pages being HTTPS, instead of looking for work-arounds. The reasons: 1: Search Positioning - Google, Bing, etc… give higher scores to secure https pages 2: User trust - users have a higher trust of https pages, and more likely to buy 3: Time spent - you will spend just as much time searching for a work-around and implementing it. If the concern is the cost of SSL for the other domain, just use LetsEncrypt, its free and simple to setup.