GoAccess-NPMLogs
GoAccess for Nginx Proxy Manager is a preconfigured Docker container that parses Nginx Proxy Manager, Traefik, and Caddy reverse-proxy logs into interactive,…
Platform availability
Available on 1 of 10 platforms
- Unraid
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
57/100 Fair
- Maintained
- 53last commit 201 days ago
- Popular
- 57715 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- 100100 MB minimum RAM, runs on ARM
Availability: platform listings confirmed today, links checked 53 days ago
- GitHub stars
- 715
- Open issues
- 15
- Last commit
- 2026-05-03
- Latest release
- v1.1.40
- License
- MIT
- Activity
- stale
Checked 20 days ago - source: GitHub (xavier-hernandez/goaccess-for-nginxproxymanager)
Resources & Compatibility
Minimum requirements: 100 MB RAM. ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Point GoAccess at your NPM log file Tell GoAccess where the access log is (often -f access.log) and where to write the report with -o, for example an HTML file your web server can show. If the log path or output is missing, GoAccess has nothing to analyze or nowhere to save the report. source
- Open the live-report WebSocket port If you start GoAccess with --real-time-html, it also starts a WebSocket server (a live browser connection) so the page can update, usually on port 9870. If that port is blocked, the report may open but it will not keep refreshing. source
- Match the date/time format and timezone Set --datetime-format to the format in your NPM log and --tz to your timezone, because GoAccess needs to understand each line. If these do not match, entries can be skipped or shown in the wrong time/day. source
Fetched 54 days ago - each note links to its source
Variants
Alternatives (10)
- AWStats - AWStats is a free powerful and featureful tool that generates advanced web, streaming, ftp or mail server statistics, graphically.
- GoAccess - GoAccess is an open-source, real-time web log analyzer and interactive viewer that runs in a *nix terminal or generates live, browser-frien…
- Google Analytics - Gain insights into website traffic with Advanced Segmentation, Custom Reporting, and data visualization.
- Matomo - Matomo is a free and open source web analytics platform that runs on your own PHP/MySQL web server, tracking your websites' traffic and del…
- PostHog - PostHog provides open-source product analytics, built for developers.
- Prisme Analytics - Prisme is an open-source, privacy-friendly web analytics service for tracking your website or web application.
- Shynet
- Tianji - Tianji is a self-hosted website analytics and uptime monitoring platform that combines visitor traffic insights, service availability check…
- Traffic Source Tarballer - This application packages the source code for the Apache Traffic Control software into a single file.
- Uplifter
Checked 40 days ago - source: AlternativeTo
Common questions
Which port must be reachable for live HTML reports to keep updating?
When started with --real-time-html, GoAccess starts a WebSocket server, usually on port 9870. If that port is blocked, the report may open but it will not keep refreshing.
How do I specify the NPM access log and report output?
Tell GoAccess where the access log is, often with -f access.log, and where to write the report with -o, for example an HTML file your web server can show. If the log path or output is missing, GoAccess has nothing to analyze or nowhere to save the report.
What configuration is needed to avoid skipped entries or wrong timestamps?
Set --datetime-format to the format in your NPM log and --tz to your timezone. If these do not match, entries can be skipped or shown in the wrong time or day.
Does the image support log sources besides Nginx Proxy Manager?
It is designed to parse and analyze logs from Nginx Proxy Manager, Traefik, and Caddy.
Answers sourced from goaccess.io, selfhost.directory
Community
- Looking for a better GoAccess for reverse proxy logs - Reddit (reddit)
- Nginx Proxy Manager (NPM) Dashboard [GoAccess] : r/selfhosted - Reddit (reddit)
- Go set up "GoAccess" on the access logs of your main reverse ... - Reddit (reddit)
- Nginx Proxy Manager + Goacces @ same server : r/selfhosted - Reddit (reddit)
- Using GoAccess with Nginx for self-hosted web analytics - Reddit (reddit)
- r/selfhosted on Reddit: A question about GoAccess stats. Is anyone ... (reddit)
Collected 53 days ago - public community threads