Open pucherot opened 11 months ago
It shouldn't be processing that file, per the filters set in place. Can you provide your docker setup, so I can test on my end?
This is my docker-compose.yml
Thank you in advance.
services:
proxy:
image: jc21/nginx-proxy-manager
container_name: proxy
restart: unless-stopped
network_mode: bridge
ports:
- 80:80
- 81:81
- 443:443
volumes:
- ./data:/data
- ./letsencrypt:/etc/letsencrypt
environment:
- TZ=Europe/Madrid
- PUID=1000
- PGID=1000
- DISABLE_IPV6=true
goaccess:
image: xavierh/goaccess-for-nginxproxymanager
container_name: proxy-goaccess
restart: unless-stopped
network_mode: bridge
ports:
- 7880:7880
volumes:
- ./data/logs:/opt/log
environment:
- TZ=Europe/Madrid
- PUID=1000
- PGID=1000
# - SKIP_ARCHIVED_LOGS=False
# - DEBUG=False
# - BASIC_AUTH=True
# - BASIC_AUTH_USERNAME=admin
# - BASIC_AUTH_PASSWORD=PASSWORD
- EXCLUDE_IPS=127.0.0.1
- LOG_TYPE=NPM+ALL
When running npm with a custom user:
Warn occur when processing the
nginx.conf
file, and this warn is logged atfallback_error.log
:goaccess attempts to process these warns as access errors, but the format of the line is not as expected.
The goaccess container log shows:
I think goaccess should filter fallback_error.log files