# Use nginx can not connection perspective login page

**URL:** <https://forum.inductiveautomation.com/t/use-nginx-can-not-connection-perspective-login-page/102964>\
**Category:** Ignition\
**Tags:** perspective, ignition81\
**Created:** [February 27, 2025, 9:02am UTC](https://forum.inductiveautomation.com/t/use-nginx-can-not-connection-perspective-login-page/102964 "2025-02-27T09:02:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pofer\_Wang](https://avatars.discourse-cdn.com/v4/letter/p/f4b2a3/32.png) [@Pofer\_Wang](https://forum.inductiveautomation.com/u/Pofer_Wang)\
**Post date:** [February 27, 2025, 9:02am UTC](https://forum.inductiveautomation.com/t/use-nginx-can-not-connection-perspective-login-page/102964/1 "2025-02-27T09:02:49Z")

</div>

Hello,

I am currently using Nginx as a reverse proxy for the Ignition SCADA Perspective client.

All my pages are functioning normally, but I am unable to use the **LOGIN** interface.

Below is the error I encountered, along with my Nginx configuration file.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/e/0e4f756e6f7fec2fa428a2c5061162ed0e791af2.jpeg)  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/9/894eececba3aa651d8476dab870f7318e529b7ed.png)

```python

server {
    listen 443 ssl;
    server_name _;

        proxy_http_version 1.1;                    
        proxy_set_header Upgrade $http_upgrade;        
        proxy_set_header Connection "upgrade";
        underscores_in_headers on;

    ssl_certificate /root/selfsigned.crt; # 自簽憑證
    ssl_certificate_key /root/selfsigned.key; # 自簽私鑰

    location ^~ /data/ {
        proxy_pass http://192.168.247.130:8088/data/;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_pass_request_headers on;
        proxy_cache_bypass $http_upgrade;
    }

    location ^~ /system/ {
        proxy_pass http://192.168.247.130:8088/system/;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_pass_request_headers on;
        proxy_cache_bypass $http_upgrade;
    }

    location ^~ /res/ {
        proxy_pass http://192.168.247.130:8088/res/;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_pass_request_headers on;
        proxy_cache_bypass $http_upgrade;
    }

    location ^~ /idp/ {
        proxy_pass http://192.168.247.130:8088/idp/;
	proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_pass_request_headers on;
        proxy_cache_bypass $http_upgrade;
    }

    

    location ^~ /.well-known/ {
        proxy_pass http://192.168.247.130:8088/.well-known/;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_pass_request_headers on;
        proxy_cache_bypass $http_upgrade;
    }

    location / {
        proxy_pass http://192.168.247.130:8088/data/perspective/client/Edge/;
	proxy_http_version 1.1;
        proxy_set_header Host $host;
	proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
	proxy_pass_request_headers on;
        proxy_cache_bypass $http_upgrade;

    }
}

```

---

<div class="post-metadata">

**Author:** ![matthew.ayre](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matthew.ayre/32/19499_2.png) [@matthew.ayre](https://forum.inductiveautomation.com/u/matthew.ayre)\
**Post date:** [April 8, 2025, 3:06pm UTC](https://forum.inductiveautomation.com/t/use-nginx-can-not-connection-perspective-login-page/102964/2 "2025-04-08T15:06:30Z")

</div>

Hi @Pofer_Wang, is it because the login redirection is using https and everything is configured for http?

When it redirects to the idp url (second image), can you remove the 's', for example

> [http://192.168.247.130/idp/](http://192.168.247.130/idp/)...

It's been a long time since setting up an nginx reverse proxy, so I could be wrong 😅