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

Ignition
1

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

# 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
image902×457 111 KB

2

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 ; But I still have the same issues.

Any update is appreciated.

3

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

4

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”

5

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.