# Perspective with nginx and a location other than / results in errors

**URL:** <https://forum.inductiveautomation.com/t/perspective-with-nginx-and-a-location-other-than-results-in-errors/33303>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [March 23, 2020, 2:31am UTC](https://forum.inductiveautomation.com/t/perspective-with-nginx-and-a-location-other-than-results-in-errors/33303 "2020-03-23T02:31:22Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jburt](https://avatars.discourse-cdn.com/v4/letter/j/7bcc69/32.png) [@jburt](https://forum.inductiveautomation.com/u/jburt)\
**Post date:** [March 23, 2020, 2:31am UTC](https://forum.inductiveautomation.com/t/perspective-with-nginx-and-a-location-other-than-results-in-errors/33303/1 "2020-03-23T02:31:22Z")

</div>

The page loads, but displays a white screen as it can’t load resources.

```auto
# cat nginx.conf
events { }
http {
    server {
        listen 80;

        location /ignition/ {
            proxy_pass http://10.59.98.114:8088/;
            proxy_buffering off;
            proxy_http_version 1.1;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection $http_connection;
            proxy_set_header Host $host;
        }

        location /guacamole/ {
            proxy_pass http://guacamole:8080/guacamole/;
            proxy_buffering off;
            proxy_http_version 1.1;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection $http_connection;
            access_log off;
        }
    }
}

```

Example Errors:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/4/401070985dba4a249f58dfa6bff44730de275134.png)

---

<div class="post-metadata">

**Author:** ![morgan.printemps](https://avatars.discourse-cdn.com/v4/letter/m/b9bd4f/32.png) [@morgan.printemps](https://forum.inductiveautomation.com/u/morgan.printemps)\
**Post date:** [June 29, 2020, 12:25pm UTC](https://forum.inductiveautomation.com/t/perspective-with-nginx-and-a-location-other-than-results-in-errors/33303/2 "2020-06-29T12:25:00Z")

</div>

Hi jburt,

Have you solved your problem ?  
I am facing the same issue.  
I have tried the solution posted here: [http://forum.inductiveautomation.com/t/reverse-proxy-rewrite-for-perspective-with-nginx-stuck-on-authenticating/31716/6](http://forum.inductiveautomation.com/t/reverse-proxy-rewrite-for-perspective-with-nginx-stuck-on-authenticating/31716/6) ; But I still have the same issues.

Any update is appreciated.

---

<div class="post-metadata">

**Author:** ![jburt](https://avatars.discourse-cdn.com/v4/letter/j/7bcc69/32.png) [@jburt](https://forum.inductiveautomation.com/u/jburt)\
**Post date:** [June 29, 2020, 2:10pm UTC](https://forum.inductiveautomation.com/t/perspective-with-nginx-and-a-location-other-than-results-in-errors/33303/3 "2020-06-29T14:10:44Z")

</div>

It works for me if you set the location to / instead of /ignition/. I was unable to figure out why.

---

<div class="post-metadata">

**Author:** ![morgan.printemps](https://avatars.discourse-cdn.com/v4/letter/m/b9bd4f/32.png) [@morgan.printemps](https://forum.inductiveautomation.com/u/morgan.printemps)\
**Post date:** [June 29, 2020, 2:18pm UTC](https://forum.inductiveautomation.com/t/perspective-with-nginx-and-a-location-other-than-results-in-errors/33303/4 "2020-06-29T14:18:35Z")

</div>

What I see as the cause of all the 404 errors, it that the folder “ignition” is removed from the response header.  
I don’t understand why, as some ressources are correctly resolved with the “ignition” folder. Those unreachable ressources are referred with absolute path like “/res/sys/js/react.js”

---

<div class="post-metadata">

**Author:** ![jburt](https://avatars.discourse-cdn.com/v4/letter/j/7bcc69/32.png) [@jburt](https://forum.inductiveautomation.com/u/jburt)\
**Post date:** [June 29, 2020, 2:23pm UTC](https://forum.inductiveautomation.com/t/perspective-with-nginx-and-a-location-other-than-results-in-errors/33303/5 "2020-06-29T14:23:45Z")

</div>

I think you’re right. Hardcoded paths in some of the resources. I’d recommend reaching out to Ignition’s support to see if they can resolve, or put in a feature request.