starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 09:25:55 +03:00

[GH-ISSUE #1944] Filename discrepancy , proxy-host-12_access.log vs proxy-host-12.log #1413

New issue

Closed

opened 2026-02-26 07:30:53 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 07:30:53 +03:00

Owner

Originally created by @xavier-hernandez on GitHub (Mar 23, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1944

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 created a docker image that is related to integrating GoAccess with NPM, https://github.com/xavier-hernandez/goaccess-for-nginxproxymanager . Recently I've had 2 users create issues related to my docker image not working for them and it ended up being that their filenames were incorrect. Since I've used NPM and the jc21 image my file names have always been something like this proxy-host-12_access.log.

These 2 users commented that their filenames are more similar to this format proxy-host-12.log. One user has confirmed that they are using justsky/goaccess-for-nginxproxymanager:latest but it's the ARM version running on a raspberry PI.

Could the difference in filename be related to the underlying architecture?

Nginx Proxy Manager Version

Both I and the user, with the problem, are running v2.9.16

Expected behavior

The filename pattern should be the same.

Screenshots

access.log                            proxy-host-12_access.log.1.gz  proxy-host-16_access.log.1.gz  proxy-host-1_error.log.5.gz    proxy-host-24_error.log.2.gz   proxy-host-4_access.log.2.gz  proxy-host-7_error.log.7.gz
default-host_access.log               proxy-host-12_access.log.2.gz  proxy-host-16_access.log.2.gz  proxy-host-1_error.log.6.gz    proxy-host-25_access.log       proxy-host-4_access.log.3.gz  proxy-host-7_error.log.8.gz
default-host_access.log.1.gz          proxy-host-12_access.log.3.gz  proxy-host-16_access.log.3.gz  proxy-host-1_error.log.7.gz    proxy-host-25_access.log.1.gz  proxy-host-4_access.log.4.gz  proxy-host-7_error.log.9.gz
default-host_access.log.2.gz          proxy-host-12_access.log.4.gz  proxy-host-16_access.log.4.gz  proxy-host-1_error.log.8.gz    proxy-host-25_access.log.2.gz  proxy-host-4_error.log        proxy-host-8_access.log

User having the issue

default.log               proxy_host-10.log  proxy_host-1.log  proxy_host-6.log
error.log                 proxy_host-11.log  proxy_host-2.log  proxy_host-7.log
fallback_access.log       proxy_host-12.log  proxy_host-3.log  proxy_host-8.log
fallback_error.log        proxy_host-13.log  proxy_host-4.log  proxy_host-9.log
letsencrypt-requests.log  proxy_host-14.log  proxy_host-5.log

Operating System

ME
Ubuntu 20.04.3 LTS (Focal Fossa)

User having the issue
RPI

Originally created by @xavier-hernandez on GitHub (Mar 23, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1944  **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 created a docker image that is related to integrating GoAccess with NPM, https://github.com/xavier-hernandez/goaccess-for-nginxproxymanager . Recently I've had 2 users create issues related to my docker image not working for them and it ended up being that their filenames were incorrect. Since I've used NPM and the jc21 image my file names have always been something like this proxy-host-12_access.log. These 2 users commented that their filenames are more similar to this format proxy-host-12.log. One user has confirmed that they are using justsky/goaccess-for-nginxproxymanager:latest but it's the ARM version running on a raspberry PI. Could the difference in filename be related to the underlying architecture? **Nginx Proxy Manager Version**  Both I and the user, with the problem, are running v2.9.16 **Expected behavior**  The filename pattern should be the same. **Screenshots**  Me ```code access.log proxy-host-12_access.log.1.gz proxy-host-16_access.log.1.gz proxy-host-1_error.log.5.gz proxy-host-24_error.log.2.gz proxy-host-4_access.log.2.gz proxy-host-7_error.log.7.gz default-host_access.log proxy-host-12_access.log.2.gz proxy-host-16_access.log.2.gz proxy-host-1_error.log.6.gz proxy-host-25_access.log proxy-host-4_access.log.3.gz proxy-host-7_error.log.8.gz default-host_access.log.1.gz proxy-host-12_access.log.3.gz proxy-host-16_access.log.3.gz proxy-host-1_error.log.7.gz proxy-host-25_access.log.1.gz proxy-host-4_access.log.4.gz proxy-host-7_error.log.9.gz default-host_access.log.2.gz proxy-host-12_access.log.4.gz proxy-host-16_access.log.4.gz proxy-host-1_error.log.8.gz proxy-host-25_access.log.2.gz proxy-host-4_error.log proxy-host-8_access.log ``` User having the issue ``` code default.log proxy_host-10.log proxy_host-1.log proxy_host-6.log error.log proxy_host-11.log proxy_host-2.log proxy_host-7.log fallback_access.log proxy_host-12.log proxy_host-3.log proxy_host-8.log fallback_error.log proxy_host-13.log proxy_host-4.log proxy_host-9.log letsencrypt-requests.log proxy_host-14.log proxy_host-5.log ``` **Operating System**  ME Ubuntu 20.04.3 LTS (Focal Fossa) User having the issue RPI

kerem

2026-02-26 07:30:53 +03:00

closed this issue
added the
stale

bug
labels

kerem commented

2026-02-26 07:30:53 +03:00

Author

Owner

@the1ts commented on GitHub (Apr 2, 2022):

The file name for logging was changed last year by the looks of it here. I'm guessing here, but as the change is in templates, proxies configured since that change will be the new proxy-host format and older proxies the proxy_host format.
Suggests you should handle both file naming schemes.

@the1ts commented on GitHub (Apr 2, 2022): The file name for logging was changed last year by the looks of it [here](https://github.com/NginxProxyManager/nginx-proxy-manager/commit/56c317d22347fabb55e97ef6ffde5bcd520f63d6). I'm guessing here, but as the change is in templates, proxies configured since that change will be the new proxy-host format and older proxies the proxy_host format. Suggests you should handle both file naming schemes.

kerem commented

2026-02-26 07:30:53 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 21, 2024):

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

@github-actions[bot] commented on GitHub (Feb 21, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 07:30:53 +03:00

Author

Owner

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

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Apr 6, 2025): Issue was closed due to inactivity.

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#1413

No description provided.

Rows
Columns