u/KHTD2004

https://preview.redd.it/1jmkh27azzxg1.png?width=1594&format=png&auto=webp&s=f125a0161690379e58d2aa0647f4abc19f9a8348

My homeserver, on wich I host a Nextcloud instance and other stuff has an automated shutdown script using ps, who and netstat to check if the server is in use and if not it updates and shuts down.

This worked very well but since the autumn update the intern loopback connections, wich used to cut of after the client connection was closed, stay active making my established system useless. I hoped for it to change back in winter update, didn't happen.

Of course I could edit my script and create a workaround for this but I'm curious, is there a reason for the connections to stay active? I changed nothing on the config of Caddy or the Nextcloud, just updates and stuff.

Relevant Sys Specs (tell me if I forgot some):

Nextcloud AIO v12.9.2

Ubuntu Server 24.04

Caddy v2.11.2

Docker version 29.1.3

reddit.com
u/KHTD2004 — 16 days ago

My homeserver, on wich I host a Nextcloud instance and other stuff has an automated shutdown script using ps, who and netstat to check if the server is in use and if not it updates and shuts down.

This worked very well but since the autumn update the intern loopback connections, wich used to cut of after the client connection was closed, stay active making my established system useless. I hoped for it to change back in winter update, didn't happen.

Of course I could edit my script and create a workaround for this but I'm curious, is there a reason for the connections to stay active? I changed nothing on the config of Caddy or the Nextcloud, just updates and stuff.

Relevant Sys Specs (tell me if I forgot some):

  • Nextcloud AIO v12.9.2
  • Ubuntu Server 24.04
  • Caddy v2.11.2
  • Docker version 29.1.3
u/KHTD2004 — 16 days ago