# Redirect Port 80 to 443

**URL:** <https://forum.inductiveautomation.com/t/redirect-port-80-to-443/78587>\
**Category:** Ignition\
**Created:** [August 30, 2023, 9:30pm UTC](https://forum.inductiveautomation.com/t/redirect-port-80-to-443/78587 "2023-08-30T21:30:11Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![plarochelle](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/plarochelle/32/29608_2.png) [@plarochelle](https://forum.inductiveautomation.com/u/plarochelle)\
**Post date:** [August 30, 2023, 9:30pm UTC](https://forum.inductiveautomation.com/t/redirect-port-80-to-443/78587/1 "2023-08-30T21:30:11Z")

</div>

Hello - we've setup a public facing server and would like to redirect any traffic to port 80 to 443. Is this something that can be done within the Ignition Web Server? FYI we changed the default 8088 and 8043 ports to 80 and 443 respectively. Would love to close 80 altogether but that would lead to a page not found for clients who use port 80.

Thanks,  
Pete

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [August 30, 2023, 9:32pm UTC](https://forum.inductiveautomation.com/t/redirect-port-80-to-443/78587/2 "2023-08-30T21:32:50Z")

</div>

Redirecting ports is something you would do outside Ignition. Security groups in AWS, iptables on Linux, a reverse proxy, etc...

---

<div class="post-metadata">

**Author:** ![plarochelle](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/plarochelle/32/29608_2.png) [@plarochelle](https://forum.inductiveautomation.com/u/plarochelle)\
**Post date:** [August 30, 2023, 9:33pm UTC](https://forum.inductiveautomation.com/t/redirect-port-80-to-443/78587/3 "2023-08-30T21:33:40Z")

</div>

thanks for the prompt response, @Kevin.Herron!

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [August 30, 2023, 9:34pm UTC](https://forum.inductiveautomation.com/t/redirect-port-80-to-443/78587/4 "2023-08-30T21:34:53Z")

</div>

You probably shouldn't redirect 80 to 443, just turn on Force Secure Redirect: [Web Server Settings - Ignition User Manual 8.1 - Ignition Documentation](https://docs.inductiveautomation.com/display/DOC81/Web+Server+Settings)

With this, you may not need an external redirection at all.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [August 30, 2023, 10:02pm UTC](https://forum.inductiveautomation.com/t/redirect-port-80-to-443/78587/5 "2023-08-30T22:02:33Z")

</div>

If you are using Let's Encrypt for your certificates, it is important to **not** redirect port 80 to 443 when the URL starts with `.well-known/`, or you won't be able to renew. This is easy to do with a load balancer or public-facing reverse proxy.

---

<div class="post-metadata">

**Author:** ![plarochelle](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/plarochelle/32/29608_2.png) [@plarochelle](https://forum.inductiveautomation.com/u/plarochelle)\
**Post date:** [August 30, 2023, 11:17pm UTC](https://forum.inductiveautomation.com/t/redirect-port-80-to-443/78587/6 "2023-08-30T23:17:05Z")

</div>

Thanks @Kevin.Herron - that didnt come up in a search but I didnt search TFM - just google. We'll try that out and let you know how it goes - that is exactly what we were looking for.