[GH-ISSUE #3536] Adding a Custom Location to a proxy host takes it offline #2352

Open
opened 2026-02-26 07:35:12 +03:00 by kerem · 20 comments
Owner

Originally created by @jricardooliveira on GitHub (Feb 9, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3536

Are you in the right place?

  • Yes

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

  • I installed NPM from docker hub latest. I add a proxy host to forward traffic to a host on my network on port 8080. It works ok. I managed also to add a Letencrypt SSL certificate without any issue. I can reach my site with the domain name.
  • If I try to add a custom location for instance for /myapp and point it to another IP on same network as previous and port 9090 it takes proxy host offline after saving

Nginx Proxy Manager Version
v2.11.1

This appears to have happened in the past. https://github.com/NginxProxyManager/nginx-proxy-manager/issues/929

Joao

Originally created by @jricardooliveira on GitHub (Feb 9, 2024). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3536 Are you in the right place? - Yes **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** - I installed NPM from docker hub latest. I add a proxy host to forward traffic to a host on my network on port 8080. It works ok. I managed also to add a Letencrypt SSL certificate without any issue. I can reach my site with the domain name. - If I try to add a custom location for instance for /myapp and point it to another IP on same network as previous and port 9090 it takes proxy host offline after saving **Nginx Proxy Manager Version** v2.11.1 This appears to have happened in the past. https://github.com/NginxProxyManager/nginx-proxy-manager/issues/929 Joao
Author
Owner

@lug-gh commented on GitHub (Feb 9, 2024):

#3512

<!-- gh-comment-id:1935997720 --> @lug-gh commented on GitHub (Feb 9, 2024): #3512
Author
Owner

@sueess86 commented on GitHub (Feb 9, 2024):

I am facing the same issue

<!-- gh-comment-id:1936503701 --> @sueess86 commented on GitHub (Feb 9, 2024): I am facing the same issue
Author
Owner

@engkad commented on GitHub (Feb 10, 2024):

Had the same issue, posted on reddit about it and using version 2.10.4 fixes it.

<!-- gh-comment-id:1937176955 --> @engkad commented on GitHub (Feb 10, 2024): Had the same issue, [posted on reddit](https://www.reddit.com/r/nginxproxymanager/comments/1aigusn/custom_locations_break_config_when_proxy_directed/) about it and using version 2.10.4 fixes it.
Author
Owner

@gitwildnow commented on GitHub (Feb 11, 2024):

I have the same problem with anything after v2.10.4. Running docker in a Ubuntu 20.04.6 VM. A custom location can't be saved regardless of how trivial it is. Revert to 2.10.4 and it works.

<!-- gh-comment-id:1937798452 --> @gitwildnow commented on GitHub (Feb 11, 2024): I have the same problem with anything after v2.10.4. Running docker in a Ubuntu 20.04.6 VM. [A custom location can't be saved](https://www.reddit.com/r/nginxproxymanager/comments/1aoab3v/cant_save_custom_locations_with_a_npm_later_than/) regardless of how trivial it is. Revert to 2.10.4 and it works.
Author
Owner

@AkshayRao27 commented on GitHub (Feb 13, 2024):

Please see if https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3512#issuecomment-1940868886 fixes the issue for you.

<!-- gh-comment-id:1940842033 --> @AkshayRao27 commented on GitHub (Feb 13, 2024): Please see if https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3512#issuecomment-1940868886 fixes the issue for you.
Author
Owner

@fabiofrances commented on GitHub (Feb 16, 2024):

I have same problem using version 2.11.1
error:
nginx: [emerg] "map" directive is not allowed here in /data/nginx/proxy_host/24.conf:53
nginx: configuration file /etc/nginx/nginx.conf test file

<!-- gh-comment-id:1948228373 --> @fabiofrances commented on GitHub (Feb 16, 2024): I have same problem using version 2.11.1 error: nginx: [emerg] "map" directive is not allowed here in /data/nginx/proxy_host/24.conf:53 nginx: configuration file /etc/nginx/nginx.conf test file
Author
Owner

@gitwildnow commented on GitHub (Feb 17, 2024):

Fixed problem by pulling jc21/nginx-proxy-manager:github-pr-3478. I can add/edit/save locations now without taking the host offline.

<!-- gh-comment-id:1950004737 --> @gitwildnow commented on GitHub (Feb 17, 2024): Fixed problem by pulling jc21/nginx-proxy-manager:github-pr-3478. I can add/edit/save locations now without taking the host offline.
Author
Owner

@AkshayRao27 commented on GitHub (Feb 17, 2024):

Fixed problem by pulling jc21/nginx-proxy-manager:github-pr-3478. I can add/edit/save locations now without taking the host offline.

How does one pull a specifc PR? My solution was to essentially do exactly this, but manually inside my install by navigating to, and editing that file. I didn't know that it was possible to deploy a specific PR ^^

<!-- gh-comment-id:1950038235 --> @AkshayRao27 commented on GitHub (Feb 17, 2024): > Fixed problem by pulling jc21/nginx-proxy-manager:github-pr-3478. I can add/edit/save locations now without taking the host offline. How does one pull a specifc PR? My solution was to essentially do exactly this, but manually inside my install by navigating to, and editing that file. I didn't know that it was possible to deploy a specific PR ^^
Author
Owner

@gitwildnow commented on GitHub (Feb 17, 2024):

I edited my config.yml to include:
image: 'jc21/nginx-proxy-manager:github-pr-3478'
You can also pull directly with docker as in:
docker pull jc21/nginx-proxy-manager:github-pr-3478

<!-- gh-comment-id:1950055135 --> @gitwildnow commented on GitHub (Feb 17, 2024): I edited my config.yml to include: image: 'jc21/nginx-proxy-manager:github-pr-3478' You can also pull directly with docker as in: docker pull jc21/nginx-proxy-manager:github-pr-3478
Author
Owner

@shanelord01 commented on GitHub (Feb 22, 2024):

I edited my config.yml to include: image: 'jc21/nginx-proxy-manager:github-pr-3478' You can also pull directly with docker as in: docker pull jc21/nginx-proxy-manager:github-pr-3478

I did this also but it bricked my config. I recommend others backup their /config and /etc/letsencrypt volumes before trying this so you can recover if things go wrong.

All working now though with the PR change in use.

<!-- gh-comment-id:1958473471 --> @shanelord01 commented on GitHub (Feb 22, 2024): > I edited my config.yml to include: image: 'jc21/nginx-proxy-manager:github-pr-3478' You can also pull directly with docker as in: docker pull jc21/nginx-proxy-manager:github-pr-3478 I did this also but it bricked my config. I recommend others backup their /config and /etc/letsencrypt volumes before trying this so you can recover if things go wrong. All working now though with the PR change in use.
Author
Owner

@NazgulCoder commented on GitHub (Mar 18, 2024):

this is insane. I'm facing the same issue, I'm not going to pull nginx-proxy-manager:github-pr-3478, i'll use custom configuration instead

<!-- gh-comment-id:2003869198 --> @NazgulCoder commented on GitHub (Mar 18, 2024): this is insane. I'm facing the same issue, I'm not going to pull nginx-proxy-manager:github-pr-3478, i'll use custom configuration instead
Author
Owner

@gitwildnow commented on GitHub (Mar 18, 2024):

What do you mean by "custom configuration"? fwiw I'm still using github-pr-3478, waiting for NPM to release something newer than the January release that does not have this fixed merge in. Apparently the merge has been done but there's no new NPM yet.

<!-- gh-comment-id:2003964714 --> @gitwildnow commented on GitHub (Mar 18, 2024): What do you mean by "custom configuration"? fwiw I'm still using github-pr-3478, waiting for NPM to release something newer than the January release that does not have this fixed merge in. Apparently the merge has been done but there's no new NPM yet.
Author
Owner

@bibstha commented on GitHub (Mar 23, 2024):

If you don't want to use the custom pr branch for security reasons, you can also use docker.io/jc21/nginx-proxy-manager:github-develop image

<!-- gh-comment-id:2016599251 --> @bibstha commented on GitHub (Mar 23, 2024): If you don't want to use the custom pr branch for security reasons, you can also use `docker.io/jc21/nginx-proxy-manager:github-develop` image
Author
Owner

@tue-kyndal commented on GitHub (Apr 22, 2024):

I have been struggling with custom locations for hours...what is going on whit this issue.
I don't what to brink my nginx..so ill wait for for a new release. Any news on this?

<!-- gh-comment-id:2070918536 --> @tue-kyndal commented on GitHub (Apr 22, 2024): I have been struggling with custom locations for hours...what is going on whit this issue. I don't what to brink my nginx..so ill wait for for a new release. Any news on this?
Author
Owner

@dudefoxlive commented on GitHub (May 2, 2024):

Has this been fixed in the latest update?

<!-- gh-comment-id:2089336056 --> @dudefoxlive commented on GitHub (May 2, 2024): Has this been fixed in the latest update?
Author
Owner

@gitwildnow commented on GitHub (May 2, 2024):

Downloaded the new 2.11.2 release and now I can add/edit custom locations again.

<!-- gh-comment-id:2090032897 --> @gitwildnow commented on GitHub (May 2, 2024): Downloaded the new 2.11.2 release and now I can add/edit custom locations again.
Author
Owner

@github-actions[bot] commented on GitHub (Dec 31, 2024):

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

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

@SimonFischer04 commented on GitHub (Jan 19, 2025):

👍

<!-- gh-comment-id:2600996475 --> @SimonFischer04 commented on GitHub (Jan 19, 2025): 👍
Author
Owner

@NazgulCoder commented on GitHub (Jan 19, 2025):

What do you mean by "custom configuration"? fwiw I'm still using github-pr-3478, waiting for NPM to release something newer than the January release that does not have this fixed merge in. Apparently the merge has been done but there's no new NPM yet.

sorry you didn't quote me so I didn't get a notification.

Anyway I moved to NPMplus and overall works better and has more features

<!-- gh-comment-id:2601004952 --> @NazgulCoder commented on GitHub (Jan 19, 2025): > What do you mean by "custom configuration"? fwiw I'm still using github-pr-3478, waiting for NPM to release something newer than the January release that does not have this fixed merge in. Apparently the merge has been done but there's no new NPM yet. sorry you didn't quote me so I didn't get a notification. Anyway I moved to NPMplus and overall works better and has more features
Author
Owner

@github-actions[bot] commented on GitHub (Sep 6, 2025):

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

<!-- gh-comment-id:3260204328 --> @github-actions[bot] commented on GitHub (Sep 6, 2025): Issue is now considered stale. If you want to keep it open, please comment :+1:
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#2352
No description provided.