Problematic update to 2.11.3 standard and proxy access log config flag no longer recognized, non-existing logs.conf not in the docker image

[neocult-de]

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 With the update to 2.11.3 since today the docker container becomes unhealthy. The eror message in the logs / console is that a logs.conf isn´t found under conf.d and that in the default.conf and in all host-configs the accesslog PATH standard and the accesslog PATH proxy is not recognized anymore.

There was probably a change as the logs.conf file did not exist before in my installations. But proxy and standard flag for the access log was recognized.

Going back to 2.11.2 immediately remmedies the issue. Problable the definition for standard and proxy logging flag were moved and the new logs.conf not added to the docker image?

Nginx Proxy Manager Version 2.11.3 is the new latest image pushed to dockerhub (Date: 2024-07-01). 2.11.2 ran without issue.

To Reproduce Updating an older installation to 2.11.3

Expected behavior Either that the old definitions for standard and proxy still work or the logs.conf is actually in the image as nginx expects with the definitions in it.

Workaround Fixing the version back to 2.11.2 will make NPM working again, seems no harm done to the config/database. Compared two installations with their respective backups.

[mdw466]

Looks like it's looking for the below in the container: letsencrypt/live/npm-27/

I renamed my current folder to "npm-27" while keeping a backup and this resolved the issue. weird one, But for now I can stick with 2.11.3 which resolve some of my cloudflare issues.

Reference: https://github.com/NginxProxyManager/nginx-proxy-manager/discussions/3349