settings page times out

[0lek]

I have installed in docker both the latest stable and the latest dev versions, both for ARM 32bit. While the container works in theory, it's unusable as I cannot access the settings page, as it times out. All the other pages work (can be accessed), but this one does not.

Nginx log gives me the following: 2022/01/10 21:53:00 [error] 424#424: *13 upstream timed out (110: Operation timed out) while reading response header from upstream, client: 10.81.0.106, server: _, request: "GET /menu/settings.php HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "10.10.10.51", referrer: "http://10.10.10.51/index.php" 2022/01/10 21:54:26 [error] 423#423: *34 upstream timed out (110: Operation timed out) while reading response header from upstream, client: 10.81.0.106, server: _, request: "GET /incl/sse/sse_data.php HTTP/1.1", upstre am: "fastcgi://127.0.0.1:9000", host: "10.10.10.51", referrer: "http://10.10.10.51/index.php" 2022/01/10 21:54:28 [error] 423#423: *42 upstream timed out (110: Operation timed out) while reading response header from upstream, client: 10.81.0.106, server: _, request: "GET /incl/sse/sse_data.php HTTP/1.1", upstre am: "fastcgi://127.0.0.1:9000", host: "10.10.10.51", referrer: "http://10.10.10.51/screen.php" 2022/01/11 16:11:52 [error] 423#423: *54 upstream timed out (110: Operation timed out) while reading response header from upstream, client: 10.81.0.106, server: _, request: "GET /menu/settings.php HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "10.10.10.51", referrer: "http://10.10.10.51/" 2022/01/11 16:11:59 [error] 423#423: *56 upstream timed out (110: Operation timed out) while reading response header from upstream, client: 10.81.0.106, server: _, request: "GET /menu/settings.php HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "10.10.10.51"

Where 10.10.10.51 is the docker, and 10.81.0.106 is the computer I try to access bbuddy via a browser. I cannot find anything anywhere that would point me into any direction unfortunately. Also often after I try to access the settings, the whole container becomes unresponsive (i.e. cannot access any page) - this seems however to stop by itself after a while.

Also the screen does not work, as it displays the websocket error. Potentially connected?

Let me know what I can do to try to uncover the cause of this.

Aleksander