I just got a kernel panic again. This time, it happened while booting the OS, not during a system update and I had to hard reboot. Also I forgot to install kdump-tools and enable kdump, so this time I'm going to do that.

Change

location ~ /\.(?!well-known) {
    deny all;
}

For now, I have set the correct swappiness value to 110 and run fsck, as I have to perform a hard reboot when a kernel panic occurs. Change the priority of this task to low until I can ensure that this won't happen again.

I cant get kernel coredump but I get this from journalctl -b -1 -r:

In T118#2122, @nawan wrote:

Also, before this, I noticed that some images weren't showing, which I think was also caused by this, so hopefully that issue will disappear too.

Setting the client_max_body_size to 100M and sending a file or image seems to have fixed the issue. Also, before this, I noticed that some images weren't showing, which I think was also caused by this, so hopefully that issue will disappear too.

From my conversation with Claude, this seems to be caused by the value of the client_max_body_size being too low.

Mereka menolak mengembalikan limit. Tidak adil memang, tetapi sudah memutuskan kalau effort yang dibutuhkan untuk uang Rp.29.900 tidak sepadan.