You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 months of running smoothly with default settings, the container suddenly stopped working properly. The Web UI showed "internal error" for any attempted changes.
Long story short, it turned out to be a storage issue. My storage limit of 4GB was full due to oversized log folders.
reading config file /etc/logrotate.d/nginx-proxy-manager
error: /etc/logrotate.d/nginx-proxy-manager:2 unknown user 'npm'
error: found error in /data/logs/*_access.log /data/logs/*/access.log , skipping
removing last 1 log configs
error: /etc/logrotate.d/nginx-proxy-manager:16 unknown user 'npm'
error: found error in /data/logs/*_error.log /data/logs/*/error.log , skipping
removing last 1 log configs
Reading state from file: /var/lib/logrotate/status
Allocating hash table for state file, size 64 entries
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
checking the logrotate configuration /etc/logrotate.d/nginx-proxy-manager:
Then run logrotate -v -f /etc/logrotate.d/nginx-proxy-manager
Optional for testing, run first logrotate -d /etc/logrotate.d/nginx-proxy-manager, to see what will happen.
The final result:
23M /data/logs
Nginx Proxy Manager Version
v2.11.1
To Reproduce
Steps to reproduce the behavior:
logrotate -d /etc/logrotate.d/nginx-proxy-manager
See error
Expected behavior
Logs in /data/logs should get rotated and compressed
Checklist
jc21/nginx-proxy-manager:latest
docker image?Describe the bug
After months of running smoothly with default settings, the container suddenly stopped working properly. The Web UI showed "internal error" for any attempted changes.
Long story short, it turned out to be a storage issue. My storage limit of 4GB was full due to oversized log folders.
The du command returned:
Root cause:
logrotate -d /etc/logrotate.d/nginx-proxy-manager
returns:checking the logrotate configuration
/etc/logrotate.d/nginx-proxy-manager
:Please note that the user npm does not exist. Instead nginx runs as root. Also, the PID-Path is wrong
FIX:
I suggest changing
/etc/logrotate.d/nginx-proxy-manager
to this:Then run
logrotate -v -f /etc/logrotate.d/nginx-proxy-manager
Optional for testing, run first
logrotate -d /etc/logrotate.d/nginx-proxy-manager
, to see what will happen.The final result:
23M /data/logs
Nginx Proxy Manager Version
v2.11.1
To Reproduce
Steps to reproduce the behavior:
logrotate -d /etc/logrotate.d/nginx-proxy-manager
Expected behavior
Logs in /data/logs should get rotated and compressed
Operating System
Proxmox, running as LXC
using release: https://api.github.com/repos/NginxProxyManager/nginx-proxy-manager/releases/latest
Additional context
The text was updated successfully, but these errors were encountered: