# \[Bug-1106\] Force Secure Redirect used when SSL is not enabled

**URL:** <https://forum.inductiveautomation.com/t/bug-1106-force-secure-redirect-used-when-ssl-is-not-enabled/46734>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [May 15, 2021, 5:22am UTC](https://forum.inductiveautomation.com/t/bug-1106-force-secure-redirect-used-when-ssl-is-not-enabled/46734 "2021-05-15T05:22:02Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![joe](https://avatars.discourse-cdn.com/v4/letter/j/b9e5f3/32.png) [@joe](https://forum.inductiveautomation.com/u/joe)\
**Post date:** [May 15, 2021, 5:22am UTC](https://forum.inductiveautomation.com/t/bug-1106-force-secure-redirect-used-when-ssl-is-not-enabled/46734/1 "2021-05-15T05:22:02Z")

</div>

With SSL enabled (via a CA-signed certificate) and the “Force Secure Redirect” option checked, I took a gateway backup and restored it on another gateway, which was missing the certificate. Ignition correctly identified that SSL was no longer configured and grayed out the HTTPS Settings pane. However, despite being disabled, the “Force Secure Redirect” checkbox was still checked, and Ignition would not allow me to connect via the Designer over the HTTP port.

The workaround was to enable the checkbox using Chrome DevTools, uncheck it, and click the Save button. A proposed fix would be to ignore the “Force Secure Redirect” setting if SSL is not configured.

 ![Screen Shot 2021-05-14 at 10.15.22 PM](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/a/7ab28ec2f5c0d37201d1e630d6eedb5770c56d81.png)

Bug confirmed in 8.1.5 running on Linux.

---

<div class="post-metadata">

**Author:** ![jspecht](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jspecht/32/6465_2.png) [@jspecht](https://forum.inductiveautomation.com/u/jspecht)\
**Post date:** [May 17, 2021, 4:21pm UTC](https://forum.inductiveautomation.com/t/bug-1106-force-secure-redirect-used-when-ssl-is-not-enabled/46734/2 "2021-05-17T16:21:12Z")

</div>

Thanks for sharing the issue. This sounds like the same issue reported here: [[BUG-1106] Web Server SSL Config Issue](http://forum.inductiveautomation.com/t/bug-1106-web-server-ssl-config-issue/42822)

We have the bug tracked in our internal ticket system and will reply back once the issue is fixed.

---

<div class="post-metadata">

**Author:** ![joe](https://avatars.discourse-cdn.com/v4/letter/j/b9e5f3/32.png) [@joe](https://forum.inductiveautomation.com/u/joe)\
**Post date:** [May 17, 2021, 4:54pm UTC](https://forum.inductiveautomation.com/t/bug-1106-force-secure-redirect-used-when-ssl-is-not-enabled/46734/3 "2021-05-17T16:54:29Z")

</div>

Oops, looks like a dupe on my part. Glad you have this already accounted for. Thanks for the update!

---

<div class="post-metadata">

**Author:** ![Nicholas\_Rodgers](https://avatars.discourse-cdn.com/v4/letter/n/77aa72/32.png) [@Nicholas\_Rodgers](https://forum.inductiveautomation.com/u/Nicholas_Rodgers)\
**Post date:** [July 19, 2022, 5:42am UTC](https://forum.inductiveautomation.com/t/bug-1106-force-secure-redirect-used-when-ssl-is-not-enabled/46734/4 "2022-07-19T05:42:55Z")

</div>

Thanks Joe, this saved me