Error: Can't define Custom locations - status "Offline" - v2.11.1 (latest)

[Gh0stExp10it]

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

Operating System Ubuntu Server 22.04.3 LTS

Additional context /None/

[tanpro260196]

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.

[tobilektri]

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

[Kavan72]

Getting same error.

[RichLii]

roll back to 2.10.4 can solve this problem

[Gh0stExp10it]

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.

[innosflew]

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

[bleak183]

roll back to 2.10.4 can solve this problem

I can confirm this works

[ramkrishna757575]

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

[jpdsc]

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.

[mbah-dukun]

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

[daraHK88]

i have the same problem

[TomRobinsonIO]

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

[MattXcz]

Same issue:

nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/2.conf:19 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/2.conf:20 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" 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 "listen ... http2" directive is deprecated, use the "http2" 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] "map" 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

[Mkeefeus]

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

[liukonen]

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

[ramkrishna757575]

I have ditched npm. Vanilla nginx is da wey

[livlif2dfullest]

I have the same issue

[AkshayRao27]

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