[GH-ISSUE #1127] Proxy Targets shown as offline #611

New issue

Closed

opened 2026-02-26 12:08:53 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 12:08:53 +03:00

Owner

Originally created by @ZTHawk on GitHub (Jun 8, 2025).
Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/1127

With version 2.1.x the "Sites List" has a column "Proxy Targets". I see that some entries have an error telling me that the proxy pass is offline.

My config:

map $http_upgrade $connection_upgrade {
    default upgrade;
    '' close;
}
upstream myUpStr {
    keepalive 32;
    keepalive_timeout 600s;
    server <local_ip>:<port>;
}
server {
    listen 80;
    listen [::]:80;
    server_name my.domain.tld;
    return 307 https://$server_name$request_uri;
}
server {
    listen 443 ssl http2;
    listen [::]:443 ssl http2;
    server_name my.domain.tld;
    ssl_certificate <MY_CERT>;
    ssl_certificate_key <MY_KEY>;
    location / {
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection $connection_upgrade;
        client_max_body_size 1000m;
        proxy_redirect off;
        add_header X-Served-By $host;
        proxy_set_header Host $host;
        proxy_set_header X-Forwarded-Scheme $scheme;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-Host $host:$server_port;
        proxy_set_header X-Forwarded-Server $host;
        proxy_pass https://myUpStr$request_uri;
    }
}

When I change proxy_pass https://myUpStr$request_uri;
to proxy_pass https://<local_ip>:<port>$request_uri;
then the warning is gone.

Originally created by @ZTHawk on GitHub (Jun 8, 2025). Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/1127 With version 2.1.x the "Sites List" has a column "Proxy Targets". I see that some entries have an error telling me that the proxy pass is offline. ![Image](https://github.com/user-attachments/assets/40167a64-bb9c-4426-a359-a7ff7568389d) My config: ``` map $http_upgrade $connection_upgrade { default upgrade; '' close; } upstream myUpStr { keepalive 32; keepalive_timeout 600s; server <local_ip>:<port>; } server { listen 80; listen [::]:80; server_name my.domain.tld; return 307 https://$server_name$request_uri; } server { listen 443 ssl http2; listen [::]:443 ssl http2; server_name my.domain.tld; ssl_certificate <MY_CERT>; ssl_certificate_key <MY_KEY>; location / { proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $connection_upgrade; client_max_body_size 1000m; proxy_redirect off; add_header X-Served-By $host; proxy_set_header Host $host; proxy_set_header X-Forwarded-Scheme $scheme; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-Host $host:$server_port; proxy_set_header X-Forwarded-Server $host; proxy_pass https://myUpStr$request_uri; } } ``` When I change `proxy_pass https://myUpStr$request_uri;` to `proxy_pass https://<local_ip>:<port>$request_uri;` then the warning is gone.