Xavier
Xavier
@masterwishx @Mission-Contro1 I deployed a new version to the develop branch. I'm adding the files now to the goaccess.conf file instead of the command line. Give it shot. docker pull...
@Mission-Contro1 and @masterwishx so I just found an issue in the current develop build that actually caused the problem that you found. It might be related to what you were...
@Mission-Contro1 can you add the debug flag if you haven't already. "DEBUG=True" and browser to /goaccess_conf.html search for this flag "#GOAN_PROXY_FILES" and provide me the output of the files listed...
Hmm... That screenshot looks good. I added a variable for the container recently called DEBUG but you got me the information I needed. - DEBUG=True Can you try skipping the...
That additional file can't be the issue. I can't figure out what might be causing the problem. Do you have any additional customizations to NPM?
@Mission-Contro1 can you post a screenshot of all your files in that directory?
@masterwishx I read the thread and I think I'd recommend as well what allinurl said. If you can run goaccess directly against the logs and see if it happens that'd...
sorry been busy for a bit, i'll get to this by the end of the week
@andyoulovexy that error usually means that it can't read the log files. Can you verify in the container by trying to access the mapped volume? Also, it doesn't look like...
I'm not familiar with that implementation. I'll set up a test environment on my end and review it. Do you know if the client IP is in the logs?