mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #1278] Problem with logrotate that it has insecure permissions #1035
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#1035
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @meibye on GitHub (Jul 31, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1278
Checklist
jc21/nginx-proxy-manager:latestdocker image?Yes
Yes
Have you searched for similar issues (both open and closed)?
Yes
Describe the bug
During start of a container with the lavest version of nginx (2.9.6) the following message is shown in the log for logrotate:
warning Error: Command failed: logrotate /etc/logrotate.d/nginx-proxy-manager
Error: skipping “/data/logs/fallback_access.log” because parent directory has insecure permissions (it’s world writable or writable by a group which is not “root”). ……
Nginx Proxy Manager Version
2.9.6
To Reproduce
Just start an app on a QNAP using a docker compose file as given in the Github README.med file.
Expected behavior
Clean startup
Screenshots
Operating System
QNAP QTS firmware version 4.5.4.1741
Additional context
Solution:
Add the following command in the /docker/rootfs/etc/cont-init.d/01_perms.sh:
chmod o-w /data/logs
@Kopernikus1979 commented on GitHub (Sep 8, 2021):
Same problem here, but on Unraid
@github-actions[bot] commented on GitHub (Mar 7, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Apr 19, 2025):
Issue was closed due to inactivity.