xavier-hernandez / goaccess-for-nginxproxymanager

GoAccess Docker Image for Nginx Proxy Manager and more...

Home Page:https://hub.docker.com/r/xavierh/goaccess-for-nginxproxymanager

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Information update

FedorAdo opened this issue · comments

Hello.
Is information only updated by restarting the container?

@FedorAdo if you mean new proxy files yes. Otherwise, the logs are continuously being read by the goaccess application in the container.

Otherwise, the logs are continuously being read by the goaccess application in the container.

docker-compose:

version: "3.9"

volumes:
nginx-pxmr_logs:
external: true

services:
nginx-pxmr:
image: jc21/nginx-proxy-manager:latest
container_name: nginx-pxmr
restart: always
ports:
- 80:80 # Public HTTP Port
- 443:443 # Public HTTPS Port
volumes:
- /home/fedor/docker/nginx-pm/data:/data
- nginx-pxmr_logs:/data/logs
- /home/fedor/docker/nginx-pm/letsencrypt:/etc/letsencrypt
environment:
DB_SQLITE_FILE: "/data/database.sqlite"
DISABLE_IPV6: "true"
networks:
default:
ipv4_address: 172.5.0.254

npm-goaccess:
container_name: npm-goaccess
image: xavierh/goaccess-for-nginxproxymanager:latest
restart: always
depends_on:
- nginx-pxmr
volumes:
- nginx-pxmr_logs:/opt/log
environment:
SKIP_ARCHIVED_LOGS: "True" #optional
DEBUG: "False" #optional
BASIC_AUTH: "True" #optional
BASIC_AUTH_USERNAME: ${USER} #optional
BASIC_AUTH_PASSWORD: ${PASSWORD} #optional
EXCLUDE_IPS: 127.0.0.1 #optional - comma delimited

networks:
default:
external:
name: application

Docker log:

...
Found (25) proxy logs...

SKIP ARCHIVED LOGS
TRUE

EXCLUDE IPS
127.0.0.1

Setting GeoIP Database
DEFAULT

DEBUG
OFF

RUN NPM GOACCESS
Daemonized GoAccess: 30

As a result, after the launch - Last Updated: 2022-07-13 11:05:20 +0700 - and that's it, it doesn't change anymore until you stop and start the container again.

@FedorAdo - can you modify this nginx-pxmr_logs:/opt/log to map to the actual place the logs are being stored?

npm-2022-07-14 100344
The problem was this - need to enable web socket. All earned. Thanks.

oh ok, I didn't know you were proxying the container via npm. Yes, the webpage requires websockets support to update the page continuously.

I'll add this to the readme file. Can I close this thread?

Can I close this thread?

Of course. Once again - thank you very much.

@FedorAdo I've updated the README file under Possible Issues with the information. Thanks!