Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
I am trying to use goaccess to analyse logs from Caddy.
GoAccess v. 1.3
GoAccess starting path:
I can access from the browser the
The console error I receive is the following:
What am I doing wrong?
From this snippet of the error that you shared...
For that to work, you'll either need to compile goaccess for TLS and configure it with a cert and key, or you'll need to reverse-proxy the websocket server using Nginx (or, in your case, Caddy, if it supports reverse-proxying websockets) - and have the webserver configured for TLS.
Thanks for the quick feedback! Indeed, I am connecting through a TLS reverse proxy. But generally everything is handled by Caddy (which automatically registers through Letsencrypt and ensures automatic http to https redirect).
If I connect through HTTP it seems working (but I will double check).
What would I need to change on goaccess in case I want to connect through TLS?
So, here is what I tried:
On the start goaccess script:
However, I still do not get the green dot...
On https://www.websocket.org/echo.html the test wss://wss.domain.com says CONNECTED.
What am I missing again?
Edit: by declaring port 443 the issue is solved: