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

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/

About this issue

  • Original URL
  • State: open
  • Created 5 months ago
  • Reactions: 7
  • Comments: 18

Most upvoted comments

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.

roll back to 2.10.4 can solve this problem

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.