starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 17:35:52 +03:00

[GH-ISSUE #1448] access_list is null #1121

New issue

Closed

opened 2026-02-26 06:35:51 +03:00 by kerem · 3 comments

kerem commented

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

Owner

Originally created by @Ewoodss on GitHub (Oct 1, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1448

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
- Yes / No
Are you sure you're not using someone else's docker image?
- Yes / No
Have you searched for similar issues (both open and closed)?
- Yes / No

Describe the bug

i acccidently choice an acces list wich i deleted in a different tab. so when the proxy was created the proxy host list gave me the error: access_list is null, even after deleting the entry via command line it still gives me the error

Nginx Proxy Manager Version

v2.9.9

To Reproduce
Steps to reproduce the behavior:

Go to 'proxy host and make a new proxy,
while this window is open go to a new tab of your browser and select acces list,
delete one here, then go back to the other tab'
in this tab create a proxy and use the acces list you just deleted in your other tab

Expected behavior

i expected to get an error about how to acces list is unaivalabe

Screenshots

Operating System

ubuntu server vm, running docker

Additional context

_nginxproxymanager_app_1_logs.txt

Originally created by @Ewoodss on GitHub (Oct 1, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1448  **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - **Yes** / No - Are you sure you're not using someone else's docker image? - **Yes** / No - Have you searched for similar issues (both open and closed)? - **Yes** / No **Describe the bug**  i acccidently choice an acces list wich i deleted in a different tab. so when the proxy was created the proxy host list gave me the error: access_list is null, even after deleting the entry via command line it still gives me the error **Nginx Proxy Manager Version**  v2.9.9 **To Reproduce** Steps to reproduce the behavior: 1. Go to 'proxy host and make a new proxy, 2. while this window is open go to a new tab of your browser and select acces list, 3. delete one here, then go back to the other tab' 4. in this tab create a proxy and use the acces list you just deleted in your other tab **Expected behavior**  i expected to get an error about how to acces list is unaivalabe **Screenshots**  ![afbeelding](https://user-images.githubusercontent.com/70382659/135637231-a797c6aa-5e99-42aa-9e51-fa6651b2a641.png) **Operating System**  ubuntu server vm, running docker **Additional context**  [_nginxproxymanager_app_1_logs.txt](https://github.com/jc21/nginx-proxy-manager/files/7267919/_nginxproxymanager_app_1_logs.txt)

kerem

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

closed this issue
added the
stale

bug
labels

kerem commented

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

Author

Owner

@the1ts commented on GitHub (Oct 18, 2021):

Not sure how to fix or improve the UI for this issue, probably best not to let this situation happen in the first place. It seems to me, we shouldn't allow removal of an access list that is active in any proxy host, redirect, stream etc, perhaps give a refusal with the problem proxy host etc supplied so the user can fix or perhaps actively remove the access list from all configurations after the user is informed where it will be removed from.
But to fix this problem proxy situation for you now, I would try to recreate the deleted access list, then you should be able to open the problem proxy host, remove the access list from that proxy host and save, then you should be able to safely remove the access list.

@the1ts commented on GitHub (Oct 18, 2021): Not sure how to fix or improve the UI for this issue, probably best not to let this situation happen in the first place. It seems to me, we shouldn't allow removal of an access list that is active in any proxy host, redirect, stream etc, perhaps give a refusal with the problem proxy host etc supplied so the user can fix or perhaps actively remove the access list from all configurations after the user is informed where it will be removed from. But to fix this problem proxy situation for you now, I would try to recreate the deleted access list, then you should be able to open the problem proxy host, remove the access list from that proxy host and save, then you should be able to safely remove the access list.

kerem commented

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

Author

Owner

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

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

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

kerem commented

2026-02-26 06:35:52 +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#1121

No description provided.

Rows
Columns