# Apache proxy perspective

**URL:** <https://forum.inductiveautomation.com/t/apache-proxy-perspective/25600>\
**Category:** Ignition Early Access\
**Created:** [June 6, 2019, 4:09am UTC](https://forum.inductiveautomation.com/t/apache-proxy-perspective/25600 "2019-06-06T04:09:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sam1](https://avatars.discourse-cdn.com/v4/letter/s/bc8723/32.png) [@sam1](https://forum.inductiveautomation.com/u/sam1)\
**Post date:** [June 6, 2019, 4:09am UTC](https://forum.inductiveautomation.com/t/apache-proxy-perspective/25600/1 "2019-06-06T04:09:30Z")

</div>

Hi everyone,

I’m currently working on a perspective project which is accessible via a public facing IP. I’m using an Apache webserver with a proxy to redirect the traffic to port 8088. This setup works if I want to access the gateway homepage, however, if I configure the proxy with the path to the client login it can’t connect (it displays the webserver homepage instead).

I’ve tried several different configurations of ProxyPass and ProxyPassReverse with no luck. Checking the Apache error and access logs hasn’t provided any insights. Is there anything that needs to be configured on the Ignition side to enable this?

I have the proxy configured as follows - any help would be greatly appreciated.

\<VirtualHost \*:80\>  
ProxyPreserveHost On  
ProxyRequests Off  
ServerName www._website_.com  
ServerAlias _website_.com  
ProxyPass /data/perspective/client/_project_/ [http://localhost:8088/](http://localhost:8088/)  
ProxyPassReverse /data/perspective/client/_project_/ [http://localhost:8088/](http://localhost:8088/)

---

<div class="post-metadata">

**Author:** ![awalker](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/awalker/32/6874_2.png) [@awalker](https://forum.inductiveautomation.com/u/awalker)\
**Post date:** [June 18, 2019, 5:07pm UTC](https://forum.inductiveautomation.com/t/apache-proxy-perspective/25600/2 "2019-06-18T17:07:56Z")

</div>

Hi @sam1,

It may be best to get in contact with support about this issue if you haven’t already.
