goaccess-for-nginxproxymanager

goaccess-for-nginxproxymanager copied to clipboard

im very sorry but i again have this issue ,maybe yo can open the old one https://github.com/xavier-hernandez/goaccess-for-nginxproxymanager/issues/28

it was running about 2 days normal then it start grow up about 10000 in second , if im not running container for some days it again working Good for 2 days ,and then again start raising Very strange i dont have this isshue on gregyankovoy/goaccess

becose i used his container befor i moved the Logs folder to /mnt/user/Logs/NginxProxyManager/ where i can look to find the problem ?

Just want to confirm that I'm also having this issue -- roughly 8,000 requests per second as reported by the web-ui.

Running the Unraid version of the image (v1.0.5) -- everything is flawless except for this one issue. Thanks for all your effort so far -- I discovered your work via a Youtube video that explained everything! https://youtu.be/-CQcEWVBjQU

Just want to confirm

Thanks, I thought I only one have this problem

@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 xavierh/goaccess-for-nginxproxymanager:develop

Give it shot

OK, Thanks a lot I will try.

I founded mostly requests going from Authelia and nextcloud also I have Uptime Kuma every 5 min. The container start OK but after some time it's going much more request. So I need to stop it for some days.

This very strange issue I didn't had this problem on old version of https://github.com/GregYankovoy

Sadly still having the same issue. It will start just fine but after a few seconds it will create the 8,000 requests once every second.

@masterwishx You and I have a very similar set up! I have Nextcloud and Uptime Kuma running as well. I will try disabling them both from NPM to see if it narrows down the issue.

I tried stopping NPM but the GoAccess request counter is still going strong.

I tried stopping NPM

I don't think the problem in them Becouse befor I used other same docker but with old version of goaccess 1.4 and was no problem. I still have it but not using for now. But I checked both and the old version does not have this issue. Now I trying the dev instead last of this docker and will post here if will be same problem.

@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 seeing in the past but just manifested itself differently this time.

Please pull the latest develop version: docker pull xavierh/goaccess-for-nginxproxymanager:develop

Still no dice -- the behavior is unchanged. Once it first loads, the counter will remain static for a few seconds before it ticks up by 8.000 requests per second.

Also the Tx. Amount ticks up very rapidly as well.

@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 after that.

Thanks for the quick reply! Where do I add the debug flag? I see there's a debug/goaccess_conf.html file when I exec into the container but it doesn't contain the flag you mentioned.

However these are the files that are listed at /goaccess-config/proxy_logs: log-file /goaccess-config/access_archive.log log-file /opt/log/proxy-host-1_access.log log-file /opt/log/proxy-host-2_access.log log-file /opt/log/proxy-host-3_access.log

Please pull the latest develop version

From yesterday dev version until today I don't see this issue, but have spikes some times not every second and still have much requests at sum I think, but maybe needs more time for checking for night I shut down server. I will update to lasted dev and will check also

Sorry but checked now problem still exist every second. Much requests and TX amount.

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 after that.

can you please explain where to add this flag ? do you mean add variable to container ?

in container console /goaccess-config # cat goaccess.conf

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 archived logs?

• SKIP_ARCHIVED_LOGS=True

OK i will try

without arhived logs should be only for 3 day log ...

I forgot to mention that i have another log file from old container of GregYankovoy called proxy_log That is still generating in NPM by some of containers , added lines "access_log /config/logs/proxy_logs.log proxy; error_log /config/log/proxy_errors.log warn;"

but in your container its read all "proxy-host-_access." what is much better way , so i dont think its make issue ?!?

i checked without arhived log the problem is still exist at end of a day

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?

No other customizations on my end -- 3 Proxy Hosts with 3 different certs through Let's Encrypt, that's all. I haven't been able to get any closer to figuring out what's wrong.

@Mission-Contro1 can you post a screenshot of all your files in that directory?

Sure -- here is /opt/logs/

Do you have any additional customizations to NPM?

No I but I use cloudflare dns proxy also. The file is still here becose issue in this container I mean I need it for check the old container but I don't have same problem in it. I have 5000 request in a day in container and in cloudflare analytic. But here I have 1000000 in 3 days. I'm also don't understand what the problem maybe its in 1.55 version. Maybe the author of program can help?

@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 be best.

If you need help with that maybe I can lend a hand.

OK, I can try but I don't know what is mean directly? Without the docker? How I can do it?

If you can help with it will be awesome

sorry been busy for a bit, i'll get to this by the end of the week

OK, Thanks