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
Not sure why goaccess would need write or execute access to my logs. Trying to run the volume as read-only results with:
...
chown: /opt/log/error.log.14.gz: Read-only file system
...```
At the very end it will give a `nginx: [alert] could not open error log file: open() "/var/lib/nginx/logs/error.log" failed (13: Permission denied)`
The text was updated successfully, but these errors were encountered:
GoAccess does not require write access to the logs. However, nginx is used in tandem with goaccess in this container to centralize goaccess services through a single port, and fix some strange websockets behavior. I believe nginx attempts to create an error.log file if it does not exist, and/or make sure it can write to it.
GoAccess does not require write access to the logs. However, nginx is used in tandem with goaccess in this container to centralize goaccess services through a single port, and fix some strange websockets behavior. I believe nginx attempts to create an error.log file if it does not exist, and/or make sure it can write to it.
What is path in unraid docker should be for /opt/log im using NginxProxyManager ?
im having same error
Not sure why goaccess would need write or execute access to my logs. Trying to run the volume as read-only results with:
The text was updated successfully, but these errors were encountered: