Since 0.9.1 I'm regularly getting gateway timeouts

[ckulka]

Since the new version 0.9.1, @Lithimlin regularly gets gateway timeouts when querying my calendars or any admin page:

baikal  | 172.30.0.3 - - [07/Apr/1982:12:45:52 +0000] "GET /res/core/BaikalAdmin/main.js HTTP/1.1" 304 0 "https://<mydomain>/admin/" "Mozilla/5.0 (X11; Linux x86_64; rv:96.0) Gecko/20100101 Firefox/96.0" "77.181.218.126"
baikal  | 1982/04/07 12:45:52 [error] 21#21: *128 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.30.0.3, server: _, request: "GET /admin/?/users/ HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.sock", host: "<mydomain>", referrer: "https://<mydomain>/admin/"
baikal  | 172.30.0.3 - - [07/Apr/1982:12:45:52 +0000] "GET /admin/?/users/ HTTP/1.1" 504 167 "https://<mydomain>/admin/" "Mozilla/5.0 (X11; Linux x86_64; rv:96.0) Gecko/20100101 Firefox/96.0" "77.181.218.126"

@mstilkerich found that the timestamps were all wrong and further tests showed that the time inside the containers worked in 0.8.0, but was all over the place in 0.9.1:

~ $ docker run --rm -it ckulka/baikal:0.9.1 date
Thu Jan  1 00:00:00 UTC 1970
~ $ docker run --rm -it ckulka/baikal:0.9.1-nginx date
Thu Jan  1 00:00:00 UTC 1970
~ $ docker run --rm -it ckulka/baikal:0.8.0 date
Wed Jan 26 10:10:14 UTC 2022
~ $ docker run --rm -it ckulka/baikal:0.8.0-nginx date
Wed Jan 26 10:10:18 UTC 2022

A very similar sounding issue at Date is wrong in container (linuxserver.io) pointed to this solution: https://docs.linuxserver.io/faq#my-host-is-incompatible-with-images-based-on-ubuntu-focal.

Originally raised by @Lithimlin in #52 (comment) , #52 (comment) , #52 (comment)

Ah, it seems that my current Raspbian is not supported anymore then.
I'm currently in the process of setting everything up so I can raze the Pi and install everything again. I'll let you know if an update helps.

I just double-checked and interestingly enough I'm already on Bullseye.
Just to make sure I updated everything but I still get the wrong date.
So I will wait until I updated the Pi and everything and let you know again whether things are working.

[Lithimlin]

With a fresh Raspbian OS (64 bit, bullseye) it is now working. So it really seems to have been connected to my upgrade from buster to bullseye not having worked 100% correctly without me realizing it before the update

[ckulka]

Happy to hear that, glad it worked out