Closed remisharrock closed 1 year ago
openresty
Are you running AGH behind a reverse proxy? Please make sure that the proxy's settings allow for longer URLs, since some of the current AGH APIs require long query strings, unfortunately.
Additionally, if you think that there are other issues, please enable verbose logs for AGH as well as look through your proxy's logs to look for clues.
Thanks for the reply, Indeed I run AGH behind NGINX configured with NGINX PROXY MANAGER (v2.10.4 ) + AUTHELIA Indeed it looks like authelia is giving me an error "Request from client exceeded the server buffer sizes." :
Oct 01 21:51:48 authelia authelia[297]: time="2023-10-01T21:51:48+02:00" level=error msg="Request from client exceeded the server buffer sizes." error="error when reading request headers: small read buffer. Increase ReadBufferSize. Buffer size=4096, contents: \"GET /api/verify HTTP/1.1\\r\\nX-Original-URL: https://adhome.remisharrock.fr/control/clients/find?ip0=2a01:e34:ec23:1280:a8f0:974e:41b4:c952&ip1=192.168.1.20&ip2=2a01:e34:ec23:6280:8f5f:b3d0:6989:5d1a&ip3\"...\",application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7\\r\\nAccept-Encoding: gzip, deflate, br\\r\\nAccept-Language: en-US,en;q=0.9\\r\\nUpg\"" method=GET path=/ remote_ip=192.168.1.109 stack="github.com/authelia/authelia/v4/internal/server/handlers.go:71 handleError.func2\ngithub.com/valyala/fasthttp@v1.43.0/server.go:2824 (*Server).writeErrorResponse\ngithub.com/valyala/fasthttp@v1.43.0/server.go:2266 (*Server).serveConn\ngithub.com/valyala/fasthttp@v1.43.0/workerpool.go:224 (*workerPool).workerFunc\ngithub.com/valyala/fasthttp@v1.43.0/workerpool.go:196 (*workerPool).getCh.func1\nruntime/asm_amd64.s:1594 goexit" status_code=431
that's a good starting point
and I solved it changing the READ SERVER BUFFER of AUTHELIA https://www.authelia.com/configuration/prologue/common/#server-buffers
"Configures the maximum request size. The default of 4096 is generally sufficient for most use cases."
For me 4096 was not sufficient.
I increased it to 8192 in the configuration like this:
server:
buffers:
read: 8192
no more problem. Thanks for the help !
Prerequisites
[X] I have checked the Wiki and Discussions and found no answer
[X] I have searched other issues and found no duplicates
[X] I want to report a bug and not ask a question or ask for help
[X] I have set up AdGuard Home correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)
Platform (OS and CPU architecture)
Linux, AMD64 (aka x86_64)
Installation
GitHub releases or script from README
Setup
On one machine
AdGuard Home version
v0.107.38
Action
going to the dashboard (/#) is not working anymore. Other pages are working like /#settings /#logs but /#clients is also not working
when I go to the dashboard I get this error in the console:
when I go to /#clients I get this error:
Expected result
to see the dashboard
Actual result
black page
Additional information and/or screenshots
No response