Today morning I got a ping from healthchecks.io, that my borgmatic backup did not run successfully. When I looked at the logs of the backup, it only had 2 lines:
/etc/borgmatic.d/immich_config.yaml: Pinging Healthchecks start

/mnt/immich-repo: Pruning archives

/etc/borgmatic.d/immich_config.yaml: Pinging Healthchecks log

/etc/borgmatic.d/immich_config.yaml: Pinging Healthchecks fail

When I tried to run it manually, it stopped at this point again, and made the whole webgui slow, then unsresponsive, then unreachable. I could reach the server through SSH. I tried to restart nginx, which made the webgui reachable, but parts of the UI were missing.

I have no idea what would cause this, i see no connection. Can someone help me and look at my diagnostics?

naspolya-diagnostics-20251031-1229.zip

Looks like an issue accessing the remote mount:

Oct 31 11:39:58 NASpolya unassigned.devices: Warning: shell_exec(/usr/bin/df '/mnt/remotes/10.10.50.5_naspolya-borg-repo' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 10.0s!
Oct 31 11:50:44 NASpolya nginx: 2025/10/31 11:50:44 [error] 1093281#1093281: *2459514 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.2.30, server: , request: "GET /sub/temperature HTTP/1.1", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php-fpm.sock", host: "192.168.2.121"
Oct 31 11:50:44 NASpolya nginx: 2025/10/31 11:50:44 [error] 1093281#1093281: *2459514 auth request unexpected status: 504 while sending to client, client: 192.168.2.30, server: , request: "GET /sub/temperature HTTP/1.1", host: "192.168.2.121"
Oct 31 11:52:35 NASpolya nginx: 2025/10/31 11:52:35 [error] 1093281#1093281: *2459815 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.2.30, server: , request: "GET /Dashboard HTTP/1.1", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php-fpm.sock", host: "192.168.2.121"
Oct 31 11:52:35 NASpolya nginx: 2025/10/31 11:52:35 [error] 1093281#1093281: *2459815 auth request unexpected status: 504 while sending to client, client: 192.168.2.30, server: , request: "GET /Dashboard HTTP/1.1", host: "192.168.2.121"

3 hours ago, JorgeB said:

Looks like an issue accessing the remote mount:

Oct 31 11:39:58 NASpolya unassigned.devices: Warning: shell_exec(/usr/bin/df '/mnt/remotes/10.10.50.5_naspolya-borg-repo' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 10.0s!
Oct 31 11:50:44 NASpolya nginx: 2025/10/31 11:50:44 [error] 1093281#1093281: *2459514 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.2.30, server: , request: "GET /sub/temperature HTTP/1.1", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php-fpm.sock", host: "192.168.2.121"
Oct 31 11:50:44 NASpolya nginx: 2025/10/31 11:50:44 [error] 1093281#1093281: *2459514 auth request unexpected status: 504 while sending to client, client: 192.168.2.30, server: , request: "GET /sub/temperature HTTP/1.1", host: "192.168.2.121"
Oct 31 11:52:35 NASpolya nginx: 2025/10/31 11:52:35 [error] 1093281#1093281: *2459815 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.2.30, server: , request: "GET /Dashboard HTTP/1.1", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php-fpm.sock", host: "192.168.2.121"
Oct 31 11:52:35 NASpolya nginx: 2025/10/31 11:52:35 [error] 1093281#1093281: *2459815 auth request unexpected status: 504 while sending to client, client: 192.168.2.30, server: , request: "GET /Dashboard HTTP/1.1", host: "192.168.2.121"

.30 is my PC that I used to reach the webgui. There was some issue with the remote indeed, the VPN did not connect. Can that cause such an unresponsive webgui?

If something is trying to use it, it might.