[GH-ISSUE #2310] Access List - Internal Error and Losing Entries #1640

Closed
opened 2026-02-26 07:31:52 +03:00 by kerem · 2 comments
Owner

Originally created by @nmbgeek on GitHub (Oct 8, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2310

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
    • Yes
  • 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
When creating and saving an access list I receive an "Internal Error" message. NPM log records this which appears to be an Express to MySQL error:
[10/8/2022] [4:32:52 AM] [Express ] › ⚠ warning connect ECONNREFUSED 172.16.0.8:3306
After closing the access list pop-up there is a new entry however not all addresses that were entered were saved. I was attempting to add all Cloudflare IPv4 address ranges plus my internal LAN so 16 total entries. Initially after entering them all and getting the error the access list that was shown had 14 rules instead of the intended 16. I opened and re-entered the addresses that were missing which were in the middle of my previous inputs. When saved I received the same 'Internal Error' message and 'ECONNREFUSED' in logs and this time the resulting entry only had 10 rules.

I will also note that when I first tried to login I received the 'Internal Error' message and 'ECONNREFUSED' from the database was logged as well. Restarting the NPM and DB resolved that and I was able to login.

Nginx Proxy Manager Version
2.9.18

To Reproduce
Steps to reproduce the behavior:

  1. Go to http://IP:81/nginx/access
  2. Click 'Add Access List'
  3. Enter a name and under Access create allow rules for Cloudflare IPs here https://www.cloudflare.com/ips-v4 (would be nice if this could be a default access rule)
  4. Click Save

Expected behavior
Access list created with entered Allow list IPs

Screenshots

Operating System
Docker on Ubuntu 20.04

Additional context
N/A

Originally created by @nmbgeek on GitHub (Oct 8, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2310 **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - Yes - 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** When creating and saving an access list I receive an "Internal Error" message. NPM log records this which appears to be an Express to MySQL error: ` [10/8/2022] [4:32:52 AM] [Express ] › ⚠ warning connect ECONNREFUSED 172.16.0.8:3306` After closing the access list pop-up there is a new entry however not all addresses that were entered were saved. I was attempting to add all Cloudflare IPv4 address ranges plus my internal LAN so 16 total entries. Initially after entering them all and getting the error the access list that was shown had 14 rules instead of the intended 16. I opened and re-entered the addresses that were missing which were in the middle of my previous inputs. When saved I received the same 'Internal Error' message and 'ECONNREFUSED' in logs and this time the resulting entry only had 10 rules. I will also note that when I first tried to login I received the 'Internal Error' message and 'ECONNREFUSED' from the database was logged as well. Restarting the NPM and DB resolved that and I was able to login. **Nginx Proxy Manager Version** 2.9.18 **To Reproduce** Steps to reproduce the behavior: 1. Go to http://IP:81/nginx/access 2. Click 'Add Access List' 3. Enter a name and under Access create allow rules for Cloudflare IPs here https://www.cloudflare.com/ips-v4 (would be nice if this could be a default access rule) 4. Click Save **Expected behavior** Access list created with entered Allow list IPs **Screenshots** <!-- If applicable, add screenshots to help explain your problem. --> **Operating System** Docker on Ubuntu 20.04 **Additional context** N/A
kerem 2026-02-26 07:31:52 +03:00
  • closed this issue
  • added the
    stale
    bug
    labels
Author
Owner

@github-actions[bot] commented on GitHub (Feb 8, 2024):

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

<!-- gh-comment-id:1933238272 --> @github-actions[bot] commented on GitHub (Feb 8, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@github-actions[bot] commented on GitHub (Mar 24, 2025):

Issue was closed due to inactivity.

<!-- gh-comment-id:2746694038 --> @github-actions[bot] commented on GitHub (Mar 24, 2025): Issue was closed due to inactivity.
Sign in to join this conversation.
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#1640
No description provided.