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 #1227] Internal error if to many text is added to advanced / custom nginx configuration #1002

New issue

Closed

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

kerem commented

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

Owner

Originally created by @mgutt on GitHub (Jul 9, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1227

I've tried to add a list of IPs which are allowed to access my server. After pressing "save" it returns only "Internal Error":

This does not happen if I add only a handful lines, so I think this is related to the amount / size of code I tried to add:

Originally created by @mgutt on GitHub (Jul 9, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1227 I've tried to add a list of IPs which are allowed to access my server. After pressing "save" it returns only "Internal Error": ![image](https://user-images.githubusercontent.com/10757176/125112124-0c198b80-e0e7-11eb-89de-68b8f080904b.png) This does not happen if I add only a handful lines, so I think this is related to the amount / size of code I tried to add: ![image](https://user-images.githubusercontent.com/10757176/125112227-2c494a80-e0e7-11eb-9e44-563dd0b27cb8.png)

kerem

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

closed this issue
added the
stale

bug
labels

kerem commented

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

Author

Owner

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

Yes, this is an error, the custom nginx configuration should be a valid configuration snippet not just a list of nginx configuration.
For simple allow ranges you should use the Access Lists feature. It allows the creation of those lists and then go to the proxy hosts you want to protect and the dropdown for access list will have the newly created access list.

@the1ts commented on GitHub (Oct 21, 2021): Yes, this is an error, the custom nginx configuration should be a valid configuration snippet not just a list of nginx configuration. For simple allow ranges you should use the Access Lists feature. It allows the creation of those lists and then go to the proxy hosts you want to protect and the dropdown for access list will have the newly created access list.

kerem commented

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

Author

Owner

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

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

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

kerem commented

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

Author

Owner

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

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Apr 20, 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#1002

No description provided.

Rows
Columns