starred/nginx-proxy-manager-NginxProxyManager
1
0
Fork 0
mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-26 01:45:54 +03:00
Code Issues 937 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #3484] Error: Can't define Custom locations - status "Offline" - v2.11.1 (latest) #2321

New issue
Closed
opened 2026-02-26 07:35:02 +03:00 by kerem · 20 comments
kerem commented 2026-02-26 07:35:02 +03:00
Owner
Copy link

Originally created by @Gh0stExp10it on GitHub (Jan 21, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3484

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
After I've upgraded to the latest version v2.11.1, I can't define Cusom locations for a Proxy Host. The status on the dashboard changes from Online🟢 to Offline🔴.
The previously existing proxy host configuration file is deleted, but not recreated (e.g.: /data/nginx/proxy_host/1.conf).

The output of the container log after pressing the "Save" button on the "Edit Proxy Host" shows the following:

[1/21/2024] [4:59:40 PM] [Global   ] › ⬤  debug     CMD: /usr/sbin/nginx -t -g "error_log off;"
[1/21/2024] [4:59:40 PM] [Nginx    ] › ⬤  debug     Deleting file: /data/nginx/proxy_host/1.conf
[1/21/2024] [4:59:40 PM] [Global   ] › ⬤  debug     CMD: /usr/sbin/nginx -t -g "error_log off;"
[1/21/2024] [4:59:40 PM] [Nginx    ] › ⬤  debug     Deleting file: /data/nginx/proxy_host/1.conf
[1/21/2024] [4:59:40 PM] [Nginx    ] › ⬤  debug     Could not delete file: {
  "errno": -2,
  "code": "ENOENT",
  "syscall": "unlink",
  "path": "/data/nginx/proxy_host/1.conf"
}
[1/21/2024] [4:59:40 PM] [Nginx    ] › ⬤  debug     Deleting file: /data/nginx/proxy_host/1.conf.err
[1/21/2024] [4:59:40 PM] [Nginx    ] › ⬤  debug     Could not delete file: {
  "errno": -2,
  "code": "ENOENT",
  "syscall": "unlink",
  "path": "/data/nginx/proxy_host/1.conf.err"
}
[1/21/2024] [4:59:40 PM] [Global   ] › ⬤  debug     CMD: /usr/sbin/nginx -t -g "error_log off;"
[1/21/2024] [4:59:40 PM] [Nginx    ] › ℹ  info      Reloading Nginx
[1/21/2024] [4:59:40 PM] [Global   ] › ⬤  debug     CMD: /usr/sbin/nginx -s reload

Nginx Proxy Manager Version
v2.11.1 (latest, as of date 21.01.2024)

To Reproduce
Steps to reproduce the behavior:

  1. Go to "Hosts" and "Proxy Hosts"
  2. Click on the three-dotted menu
  3. Click on edit
  4. Switch to the tab "Custom locations"
  5. Create a new Custom location (example see screenshot below)
  6. Click on the button "Save"
  7. The status should be now switched to Offline

Expected behavior
It should be possible to define a custom location without deleting the proxy conf and thus taking the host offline.
In version v2.10.4 this is possible without any problems. I was able to test this successfully by rolling back to this version.

Screenshots
screenshot-npm-custom-locations-01
screenshot-npm-custom-locations-02

Operating System
Ubuntu Server 22.04.3 LTS

Additional context
/None/

Originally created by @Gh0stExp10it on GitHub (Jan 21, 2024). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3484 **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** After I've upgraded to the latest version v2.11.1, I can't define ```Cusom locations``` for a ```Proxy Host```. The status on the dashboard changes from *Online*&#128994; to *Offline*&#x1F534;. The previously existing proxy host configuration file is deleted, but not recreated (e.g.: /data/nginx/proxy_host/1.conf). The output of the container log after pressing the "Save" button on the "Edit Proxy Host" shows the following: ```sh [1/21/2024] [4:59:40 PM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -t -g "error_log off;" [1/21/2024] [4:59:40 PM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/proxy_host/1.conf [1/21/2024] [4:59:40 PM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -t -g "error_log off;" [1/21/2024] [4:59:40 PM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/proxy_host/1.conf [1/21/2024] [4:59:40 PM] [Nginx ] › ⬤ debug Could not delete file: { "errno": -2, "code": "ENOENT", "syscall": "unlink", "path": "/data/nginx/proxy_host/1.conf" } [1/21/2024] [4:59:40 PM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/proxy_host/1.conf.err [1/21/2024] [4:59:40 PM] [Nginx ] › ⬤ debug Could not delete file: { "errno": -2, "code": "ENOENT", "syscall": "unlink", "path": "/data/nginx/proxy_host/1.conf.err" } [1/21/2024] [4:59:40 PM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -t -g "error_log off;" [1/21/2024] [4:59:40 PM] [Nginx ] › ℹ info Reloading Nginx [1/21/2024] [4:59:40 PM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -s reload ``` **Nginx Proxy Manager Version** v2.11.1 (latest, as of date 21.01.2024) **To Reproduce** Steps to reproduce the behavior: 1. Go to "Hosts" and "Proxy Hosts" 2. Click on the three-dotted menu 3. Click on edit 4. Switch to the tab "Custom locations" 5. Create a new Custom location (example see screenshot below) 6. Click on the button "Save" 7. The status should be now switched to *Offline* **Expected behavior** It should be possible to define a custom location without deleting the proxy conf and thus taking the host offline. In version v2.10.4 this is possible without any problems. I was able to test this successfully by rolling back to this version. **Screenshots** <img width="248" alt="screenshot-npm-custom-locations-01" src="https://github.com/NginxProxyManager/nginx-proxy-manager/assets/7295005/96a2f2c9-0f15-43d6-b543-9338d59eadcc"> <img width="113" alt="screenshot-npm-custom-locations-02" src="https://github.com/NginxProxyManager/nginx-proxy-manager/assets/7295005/7671e46c-a5a6-4486-84f9-a1d63809d1e0"> **Operating System** Ubuntu Server 22.04.3 LTS **Additional context** /None/
kerem 2026-02-26 07:35:02 +03:00
  • closed this issue
  • added the
    stale
    bug
         labels
kerem commented 2026-02-26 07:35:03 +03:00
Author
Owner
Copy link

@tanpro260196 commented on GitHub (Jan 21, 2024):

Most likely a duplicate of this: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3474
TLDR: Using HSTS and custom location at the same time break the config.

<!-- gh-comment-id:1902754478 --> @tanpro260196 commented on GitHub (Jan 21, 2024): Most likely a duplicate of this: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3474 TLDR: Using HSTS and custom location at the same time break the config.
kerem commented 2026-02-26 07:35:03 +03:00
Author
Owner
Copy link

@tobilektri commented on GitHub (Jan 22, 2024):

Same here:

2024/01/22 10:35:02 [emerg] 747#747: "map" directive is not allowed here in /data/nginx/proxy_host/10.conf:47
2024/01/22 10:35:02 [notice] 751#751: signal process started
<!-- gh-comment-id:1903709443 --> @tobilektri commented on GitHub (Jan 22, 2024): Same here: ``` 2024/01/22 10:35:02 [emerg] 747#747: "map" directive is not allowed here in /data/nginx/proxy_host/10.conf:47 2024/01/22 10:35:02 [notice] 751#751: signal process started ```
kerem commented 2026-02-26 07:35:03 +03:00
Author
Owner
Copy link

@Kavan72 commented on GitHub (Jan 23, 2024):

Getting same error.

<!-- gh-comment-id:1905220337 --> @Kavan72 commented on GitHub (Jan 23, 2024): Getting same error.
kerem commented 2026-02-26 07:35:03 +03:00
Author
Owner
Copy link

@RichLii commented on GitHub (Jan 23, 2024):

roll back to 2.10.4 can solve this problem

<!-- gh-comment-id:1905247146 --> @RichLii commented on GitHub (Jan 23, 2024): roll back to 2.10.4 can solve this problem
kerem commented 2026-02-26 07:35:03 +03:00
Author
Owner
Copy link

@Gh0stExp10it commented on GitHub (Jan 23, 2024):

Most likely a duplicate of this: #3474 TLDR: Using HSTS and custom location at the same time break the config.

Thanks for the additional info.
Unfortunately, this is not the case, HSTS is switched off/deactivated.

<!-- gh-comment-id:1905780117 --> @Gh0stExp10it commented on GitHub (Jan 23, 2024): > Most likely a duplicate of this: #3474 TLDR: Using HSTS and custom location at the same time break the config. Thanks for the additional info. Unfortunately, this is not the case, HSTS is switched off/deactivated.
kerem commented 2026-02-26 07:35:03 +03:00
Author
Owner
Copy link

@innosflew commented on GitHub (Jan 24, 2024):

I'm experiencing the same issue, and I don't use HSTS either.

<!-- gh-comment-id:1907476134 --> @innosflew commented on GitHub (Jan 24, 2024): I'm experiencing the same issue, and I don't use HSTS either.
kerem commented 2026-02-26 07:35:03 +03:00
Author
Owner
Copy link

@bleak183 commented on GitHub (Jan 24, 2024):

roll back to 2.10.4 can solve this problem

I can confirm this works

<!-- gh-comment-id:1908646947 --> @bleak183 commented on GitHub (Jan 24, 2024): > roll back to 2.10.4 can solve this problem I can confirm this works
kerem commented 2026-02-26 07:35:03 +03:00
Author
Owner
Copy link

@ramkrishna757575 commented on GitHub (Jan 25, 2024):

Same here...suddenly all my reverse proxies broke due to this

<!-- gh-comment-id:1910210475 --> @ramkrishna757575 commented on GitHub (Jan 25, 2024): Same here...suddenly all my reverse proxies broke due to this
kerem commented 2026-02-26 07:35:03 +03:00
Author
Owner
Copy link

@jpdsc commented on GitHub (Jan 25, 2024):

Same here, there is a workaround in https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3474 but will wait until resolved and reverted to :2.10.4 for now.

<!-- gh-comment-id:1910262102 --> @jpdsc commented on GitHub (Jan 25, 2024): Same here, there is a workaround in https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3474 but will wait until resolved and reverted to :2.10.4 for now.
kerem commented 2026-02-26 07:35:03 +03:00
Author
Owner
Copy link

@mbah-dukun commented on GitHub (Jan 26, 2024):

same here . . . .
is like npm not have permission for execute folder map

<!-- gh-comment-id:1911430848 --> @mbah-dukun commented on GitHub (Jan 26, 2024): same here . . . . is like npm not have permission for execute folder map
kerem commented 2026-02-26 07:35:03 +03:00
Author
Owner
Copy link

@daraHK88 commented on GitHub (Jan 28, 2024):

i have the same problem

<!-- gh-comment-id:1913546718 --> @daraHK88 commented on GitHub (Jan 28, 2024): i have the same problem
kerem commented 2026-02-26 07:35:03 +03:00
Author
Owner
Copy link

@TomRobinsonIO commented on GitHub (Jan 28, 2024):

Same issue here, HSTS on/off does not make a difference.

<!-- gh-comment-id:1913669601 --> @TomRobinsonIO commented on GitHub (Jan 28, 2024): Same issue here, HSTS on/off does not make a difference.
kerem commented 2026-02-26 07:35:03 +03:00
Author
Owner
Copy link

@MattXcz commented on GitHub (Jan 31, 2024):

Same issue:

nginx: [warn] the &quot;listen ... http2&quot; directive is deprecated, use the &quot;http2&quot; directive instead in /data/nginx/proxy_host/2.conf:19 nginx: [warn] the &quot;listen ... http2&quot; directive is deprecated, use the &quot;http2&quot; directive instead in /data/nginx/proxy_host/2.conf:20 nginx: [warn] the &quot;listen ... http2&quot; directive is deprecated, use the &quot;http2&quot; directive instead in /data/nginx/proxy_host/4.conf:19 nginx: [warn] protocol options redefined for 0.0.0.0:443 in /data/nginx/proxy_host/4.conf:19 nginx: [warn] the &quot;listen ... http2&quot; directive is deprecated, use the &quot;http2&quot; directive instead in /data/nginx/proxy_host/4.conf:20 nginx: [warn] protocol options redefined for [::]:443 in /data/nginx/proxy_host/4.conf:20 nginx: [emerg] &quot;map&quot; directive is not allowed here in /data/nginx/proxy_host/4.conf:65 nginx: configuration file /usr/local/openresty/nginx/conf/nginx.conf test failed

<!-- gh-comment-id:1919356102 --> @MattXcz commented on GitHub (Jan 31, 2024): Same issue: `nginx: [warn] the &quot;listen ... http2&quot; directive is deprecated, use the &quot;http2&quot; directive instead in /data/nginx/proxy_host/2.conf:19 nginx: [warn] the &quot;listen ... http2&quot; directive is deprecated, use the &quot;http2&quot; directive instead in /data/nginx/proxy_host/2.conf:20 nginx: [warn] the &quot;listen ... http2&quot; directive is deprecated, use the &quot;http2&quot; directive instead in /data/nginx/proxy_host/4.conf:19 nginx: [warn] protocol options redefined for 0.0.0.0:443 in /data/nginx/proxy_host/4.conf:19 nginx: [warn] the &quot;listen ... http2&quot; directive is deprecated, use the &quot;http2&quot; directive instead in /data/nginx/proxy_host/4.conf:20 nginx: [warn] protocol options redefined for [::]:443 in /data/nginx/proxy_host/4.conf:20 nginx: [emerg] &quot;map&quot; directive is not allowed here in /data/nginx/proxy_host/4.conf:65 nginx: configuration file /usr/local/openresty/nginx/conf/nginx.conf test failed `
kerem commented 2026-02-26 07:35:03 +03:00
Author
Owner
Copy link

@Mkeefeus commented on GitHub (Jan 31, 2024):

Same issue here as well, HSTS turned off and still unable to start with custom locations

<!-- gh-comment-id:1920123367 --> @Mkeefeus commented on GitHub (Jan 31, 2024): Same issue here as well, HSTS turned off and still unable to start with custom locations
kerem commented 2026-02-26 07:35:03 +03:00
Author
Owner
Copy link

@liukonen commented on GitHub (Feb 2, 2024):

Using "Latest" branch... Switching boxes because my services just stopped working... adding subdomains, and It goes to offline once the subdomain is added. HSTS does not matter

[2/2/2024] [2:48:15 AM] [Nginx ] › ⬤ debug Could not delete file: {
"errno": -2,
"code": "ENOENT",
"syscall": "unlink",
"path": "/data/nginx/proxy_host/4.conf.err"
}

If I try dropping my version, I get the following errors popping up
nginx: [emerg] "map" directive is not allowed here in /data/nginx/proxy_host/1.conf:44

<!-- gh-comment-id:1922696698 --> @liukonen commented on GitHub (Feb 2, 2024): Using "Latest" branch... Switching boxes because my services just stopped working... adding subdomains, and It goes to offline once the subdomain is added. HSTS does not matter [2/2/2024] [2:48:15 AM] [Nginx ] › ⬤ debug Could not delete file: { "errno": -2, "code": "ENOENT", "syscall": "unlink", "path": "/data/nginx/proxy_host/4.conf.err" } If I try dropping my version, I get the following errors popping up nginx: [emerg] "map" directive is not allowed here in /data/nginx/proxy_host/1.conf:44
kerem commented 2026-02-26 07:35:03 +03:00
Author
Owner
Copy link

@ramkrishna757575 commented on GitHub (Feb 4, 2024):

I have ditched npm. Vanilla nginx is da wey

<!-- gh-comment-id:1925919976 --> @ramkrishna757575 commented on GitHub (Feb 4, 2024): I have ditched npm. Vanilla nginx is da wey
kerem commented 2026-02-26 07:35:03 +03:00
Author
Owner
Copy link

@livlif2dfullest commented on GitHub (Feb 5, 2024):

I have the same issue

<!-- gh-comment-id:1927219231 --> @livlif2dfullest commented on GitHub (Feb 5, 2024): I have the same issue
kerem commented 2026-02-26 07:35:03 +03:00
Author
Owner
Copy link

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

See if this solution works for you: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3512#issuecomment-1940868886

<!-- gh-comment-id:1940874262 --> @AkshayRao27 commented on GitHub (Feb 13, 2024): See if this solution works for you: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3512#issuecomment-1940868886
kerem commented 2026-02-26 07:35:03 +03:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (Sep 5, 2024):

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

<!-- gh-comment-id:2330452234 --> @github-actions[bot] commented on GitHub (Sep 5, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
kerem commented 2026-02-26 07:35:03 +03:00
Author
Owner
Copy link

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

Issue was closed due to inactivity.

<!-- gh-comment-id:3263367841 --> @github-actions[bot] commented on GitHub (Sep 7, 2025): Issue was closed due to inactivity.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
develop
dependabot/npm_and_yarn/backend/liquidjs-10.25.7
dependabot/npm_and_yarn/frontend/prod-minor-updates-2a16bf3987
dependabot/npm_and_yarn/frontend/dev-patch-updates-754666cf41
dependabot/npm_and_yarn/backend/basic-ftp-5.3.0
dependabot/npm_and_yarn/test/follow-redirects-1.16.0
dependabot/npm_and_yarn/test/axios-1.15.0
dependabot/npm_and_yarn/frontend/lodash-4.18.1
dependabot/npm_and_yarn/backend/lodash-4.18.1
dependabot/npm_and_yarn/test/lodash-4.18.1
dependabot/npm_and_yarn/frontend/vite-7.3.2
dependabot/npm_and_yarn/backend/prod-minor-updates-5ec19a7f21
dependabot/npm_and_yarn/frontend/lodash-es-4.18.1
dependabot/npm_and_yarn/frontend/happy-dom-20.8.9
dependabot/npm_and_yarn/backend/path-to-regexp-8.4.0
dependabot/npm_and_yarn/frontend/picomatch-4.0.4
dependabot/npm_and_yarn/backend/picomatch-2.3.2
dependabot/npm_and_yarn/frontend/yaml-1.10.3
dependabot/npm_and_yarn/test/flatted-3.4.2
dependabot/npm_and_yarn/test/tar-7.5.11
dependabot/npm_and_yarn/frontend/immutable-5.1.5
master
dependabot/npm_and_yarn/test/glob-10.5.0
dependabot/npm_and_yarn/frontend/mdast-util-to-hast-13.2.1
dependabot/npm_and_yarn/test/form-data-4.0.4
v3-abandoned
bump-freedns
openidc
ssl-passthrough-hosts
static-content
v2.14.0
v2.13.7
v2.13.6
v2.13.5
v2.13.4
v2.13.3
v2.13.2
v2.13.1
v2.13.0
v2.12.6
v2.12.5
v2.12.4
v2.12.3
v2.12.2
v2.12.1
v2.12.0
v2.11.3
v2.11.2
v2.11.1
v2.11.0
v2.10.4
v2.10.3
v2.10.2
v2.10.1
v2.10.0
v2.9.22
v2.9.21
v2.9.20
v2.9.19
v2.9.18
v2.9.17
v2.9.16
v2.9.15
v2.9.14
v2.9.13
v2.9.12
v2.9.11
v2.9.10
v2.9.9
v2.9.8
v2.9.7
v2.9.6
v2.9.5
v2.9.4
v2.9.3
v2.9.2
v2.9.1
v2.9.0
v2.8.1
v2.8.0
v2.7.3
v2.7.2
v2.7.1
v2.7.0
v2.6.2
v2.6.1
v2.6.0
v2.5.0
v2.4.0
v2.3.1
v2.3.0
v2.2.4
v2.2.3
v2.2.2
v2.2.1
v2.2.0
v2.1.2
v2.1.1
v2.1.0
2.0.14
2.0.13
2.0.12
2.0.11
2.0.10
2.0.9
2.0.8
2.0.7
2.0.6
2.0.5
2.0.4
2.0.3
2.0.2
2.0.0
v2.0.0
1.1.2
1.1.1
1.0.1
Labels
Clear labels   
awaiting feedback

   
bug

   
cannot reproduce

   
dns provider request

   
duplicate

   
enhancement

   
enhancement

   
enhancement

   
good first issue

   
help wanted

   
invalid

   
need more info

   
no certbot plugin available

   
product-support

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
stale

   
troll

   
upstream issue

   
v2

   
v2

   
v2

   
v3

   
wontfix
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#2321
No description provided.