redirect the output to a subdomain about docker-goaccess HOT 3 CLOSED

Hi @Habak1. How is the subdomain pointed to the container? You'll want to make sure it's using at least HTTP 1.1 and allows for connection upgrades for websockets. There's an example available in the readme for nginx.

location ^~ /goaccess {
    resolver 127.0.0.11 valid=30s;
    set $upstream_goaccess goaccess;
    proxy_pass http://$upstream_goaccess:7889/;

    proxy_connect_timeout 1d;
    proxy_send_timeout 1d;
    proxy_read_timeout 1d;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "Upgrade";
}

In regards to the different ports, I believe you want to run multiple instances of his container on different ports? This should be possible through native docker arguments. The README provides a sample command to map TCP port 7889 to the container port of 7889. This can be changed to suit your needs. For instance, you can use the below to expose the container on port 8080 of the host:
docker run --name goaccess -p 8080:7889 -v /path/to/host/nginx/logs:/opt/log -v /path/to/goaccess/storage:/config -d gregyankovoy/goaccess

from docker-goaccess.

Thank you very much for the tips. I will try the days to understand and implement it and then report back.

from docker-goaccess.

Hi Greg,
thank you very much for the hints. Now everything works fine.

from docker-goaccess.