starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-26 01:45:54 +03:00

[GH-ISSUE #1440] Access list not set in proxy host after disable/enable #1118

New issue

Closed

opened 2026-02-26 06:35:50 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 06:35:50 +03:00

Owner

Originally created by @richard7ac on GitHub (Sep 28, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1440

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
- Yes - I think so - shows 2.9.9 in the GUI and it was created 2 weeks ago vs online latest 20 days
Are you sure you're not using someone else's docker image?
- Yes
Have you searched for similar issues (both open and closed)?
- Yes

Describe the bug

Access List not re-applied to proxy host on re-enablement

Nginx Proxy Manager Version

2.9.9

To Reproduce
Steps to reproduce the behavior:

Create an access list.
Create a proxy host and apply access list. Ensure it is enabled.
Check config in /data/nginx/proxy_host ... Access list expanded correctly.
Disable and reenable and check again.
Config now has deny all only!!
Change Access list for proxy and change it back all OK again!

Expected behavior

I would expect that re-enabling the proxy host would bring it back with the Access List as shown in the GUI

Screenshots

Before Disabled

server {
  set $forward_scheme http;
  set $server         "IPADDRESS";
  set $port           80;
  listen 80;
#listen [::]:80;
listen 443 ssl http2;
#listen [::]:443;
  server_name SERVERURL;
  # Let's Encrypt SSL
  include conf.d/include/letsencrypt-acme-challenge.conf;
  include conf.d/include/ssl-ciphers.conf;
  ssl_certificate /etc/letsencrypt/live/npm-17/fullchain.pem;
  ssl_certificate_key /etc/letsencrypt/live/npm-17/privkey.pem;
  access_log /data/logs/proxy-host-16_access.log proxy;
  error_log /data/logs/proxy-host-16_error.log warn;
  location / {
    # Access Rules
    allow 192.168.0.0/16;
    allow 10.0.0.0/8;
    allow 172.16.0.0/12;
    deny all;
    # Access checks must...
    satisfy all;
    # Proxy!
    include conf.d/include/proxy.conf;
  }
  # Custom
  include /data/nginx/custom/server_proxy[.]conf;
}

Disabled File no longer exists

Re-Enabled

server {
  set $forward_scheme http;
  set $server         "IPADDRESS";
  set $port           80;
  listen 80;
#listen [::]:80;
listen 443 ssl http2;
#listen [::]:443;
  server_name SERVERURL;
  # Let's Encrypt SSL
  include conf.d/include/letsencrypt-acme-challenge.conf;
  include conf.d/include/ssl-ciphers.conf;
  ssl_certificate /etc/letsencrypt/live/npm-17/fullchain.pem;
  ssl_certificate_key /etc/letsencrypt/live/npm-17/privkey.pem;
  access_log /data/logs/proxy-host-16_access.log proxy;
  error_log /data/logs/proxy-host-16_error.log warn;
  location / {
    # Access Rules
    deny all;
    # Access checks must...
    satisfy all;
    # Proxy!
    include conf.d/include/proxy.conf;
  }
  # Custom
  include /data/nginx/custom/server_proxy[.]conf;
}

Operating System

Raspberry Pi 4 using Portainer to deploy NPM

Additional context

Originally created by @richard7ac on GitHub (Sep 28, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1440  **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - Yes - I think so - shows 2.9.9 in the GUI and it was created 2 weeks ago vs online latest 20 days - Are you sure you're not using someone else's docker image? - Yes - Have you searched for similar issues (both open and closed)? - Yes **Describe the bug**  Access List not re-applied to proxy host on re-enablement **Nginx Proxy Manager Version**  2.9.9 **To Reproduce** Steps to reproduce the behavior: 1. Create an access list. 2. Create a proxy host and apply access list. Ensure it is enabled. 3. Check config in /data/nginx/proxy_host ... Access list expanded correctly. 4. Disable and reenable and check again. 5. Config now has deny all only!! 6. Change Access list for proxy and change it back all OK again! **Expected behavior**  I would expect that re-enabling the proxy host would bring it back with the Access List as shown in the GUI **Screenshots**  Before Disabled ``` server { set $forward_scheme http; set $server "IPADDRESS"; set $port 80; listen 80; #listen [::]:80; listen 443 ssl http2; #listen [::]:443; server_name SERVERURL; # Let's Encrypt SSL include conf.d/include/letsencrypt-acme-challenge.conf; include conf.d/include/ssl-ciphers.conf; ssl_certificate /etc/letsencrypt/live/npm-17/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/npm-17/privkey.pem; access_log /data/logs/proxy-host-16_access.log proxy; error_log /data/logs/proxy-host-16_error.log warn; location / { # Access Rules allow 192.168.0.0/16; allow 10.0.0.0/8; allow 172.16.0.0/12; deny all; # Access checks must... satisfy all; # Proxy! include conf.d/include/proxy.conf; } # Custom include /data/nginx/custom/server_proxy[.]conf; } ``` Disabled File no longer exists Re-Enabled ``` server { set $forward_scheme http; set $server "IPADDRESS"; set $port 80; listen 80; #listen [::]:80; listen 443 ssl http2; #listen [::]:443; server_name SERVERURL; # Let's Encrypt SSL include conf.d/include/letsencrypt-acme-challenge.conf; include conf.d/include/ssl-ciphers.conf; ssl_certificate /etc/letsencrypt/live/npm-17/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/npm-17/privkey.pem; access_log /data/logs/proxy-host-16_access.log proxy; error_log /data/logs/proxy-host-16_error.log warn; location / { # Access Rules deny all; # Access checks must... satisfy all; # Proxy! include conf.d/include/proxy.conf; } # Custom include /data/nginx/custom/server_proxy[.]conf; } ``` **Operating System**  Raspberry Pi 4 using Portainer to deploy NPM **Additional context**

kerem

2026-02-26 06:35:50 +03:00

closed this issue
added the
stale

bug
labels

kerem commented

2026-02-26 06:35:50 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 4, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Mar 4, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 06:35:50 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 16, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Apr 16, 2025): Issue was closed due to inactivity.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#1118

No description provided.

Rows
Columns