# NGINX reverse proxy configuration

**URL:** <https://forum.inductiveautomation.com/t/nginx-reverse-proxy-configuration/106269>\
**Category:** Ignition\
**Created:** [May 14, 2025, 6:16pm UTC](https://forum.inductiveautomation.com/t/nginx-reverse-proxy-configuration/106269 "2025-05-14T18:16:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Henrique\_Trebilcock](https://avatars.discourse-cdn.com/v4/letter/h/8edcca/32.png) [@Henrique\_Trebilcock](https://forum.inductiveautomation.com/u/Henrique_Trebilcock)\
**Post date:** [May 14, 2025, 6:16pm UTC](https://forum.inductiveautomation.com/t/nginx-reverse-proxy-configuration/106269/1 "2025-05-14T18:16:16Z")

</div>

Hello community,  
I have an ignition running in a docker container and a nginx reverse proxy. he reverse proxy is configured to expose Ignition under a prefixed path, such as `/ignition` , using a URL like:  
_[http://localhost/ignition/web/home](http://localhost/ignition/web/home)_

We use the following Nginx settings:  
location /ignition/ { rewrite ^/ignition(/.\*)$ /$1 break; proxy\_pass [http://localhost:9088](http://localhost:9088); proxy\_http\_version 1.1; proxy\_set\_header Host $host; proxy\_set\_header X-Real-IP $remote\_addr; proxy\_set\_header X-Forwarded-For $proxy\_add\_x\_forwarded\_for; proxy\_set\_header X-Forwarded-Proto $scheme; proxy\_set\_header X-Forwarded-Prefix /ignition; proxy\_set\_header X-Forwarded-Host $host; proxy\_set\_header X-Forwarded-Port $server\_port; proxy\_set\_header Upgrade $http\_upgrade; proxy\_set\_header Connection "upgrade"; }

Inside the Ignition Gateway, we have:  
Use Proxy Forwarded Headers = True  
Resolve Client Hostnames = False

Despite this, Ignition continues to respond with redirects like:  
Location: [http://localhost/web/home?0](http://localhost/web/home?0)

…instead of respecting the prefix and returning:  
Location: [http://localhost/ignition/web/home?0](http://localhost/ignition/web/home?0)

We have confirmed that:  
`X-Forwarded-Prefix: /ignition` is being received by Ignition (tested with `curl`)

- Proxy forwarding headers are correctly sent

Does anyone had this kind of issue before?

---

<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:** [May 14, 2025, 6:31pm UTC](https://forum.inductiveautomation.com/t/nginx-reverse-proxy-configuration/106269/2 "2025-05-14T18:31:53Z")

</div>

Proxying Ignition in a subfolder is simply not supported.