bug: Container status unhealthy, service not reachable

[xiskyliner]

Describe the bug

Hello everyone,
i´ve been using Homarr for just over a week and up until yesterday it worked perfectly.
The only thing I did was edit my dashboard and add a couple of apps, so I have no clue why its happening.

Now, every couple of hours and sometimes even just a few minutes apart, the container status changes to unhealthy and the dashboard isnt reachable anymore, without the container/stack stopping entirely.
I can restart the stack manually and it will work temporarily.

After encountering the issue, I updated the Image and redeployed the Stack + I already tried disabling every task in Homarr so it doesnt process any integration or app data - didnt help.

The logs didnt help me either.

Steps to reproduce

Docker Compose Stack in Dockhand:

services:
homarr:
container_name: Homarr
image: ghcr.io/homarr-labs/homarr:latest
healthcheck:
test: ["CMD-SHELL", "nc -z 127.0.0.1 7575 || exit 1"]
interval: 10s
timeout: 5s
retries: 3
start_period: 90s
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- /volume4/docker/homarr:/appdata:rw
environment:
SECRET_ENCRYPTION_KEY: ...
ports:
- 7575:7575
restart: on-failure:5

Logs at Crash:

[Homarr] 2026-05-04T23:09:16.030546407Z 22:M 04 May 2026 23:09:16.030 * Background saving started by pid 3465
[Homarr] 2026-05-04T23:09:16.038803711Z 3465:C 04 May 2026 23:09:16.038 * BGSAVE done, 34 keys saved, 0 keys skipped, 29259 bytes written.
[Homarr] 2026-05-04T23:09:16.059744481Z 3465:C 04 May 2026 23:09:16.055 * DB saved on disk
[Homarr] 2026-05-04T23:09:16.059810967Z 3465:C 04 May 2026 23:09:16.056 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
[Homarr] 2026-05-04T23:09:16.130583578Z 22:M 04 May 2026 23:09:16.130 * Background saving terminated with success
[Homarr] 2026-05-04T23:09:56.669188681Z Killed
[Homarr] 2026-05-04T23:09:56.670112091Z Received SIGTERM. Shutting down...
[Homarr] 2026-05-04T23:09:56.738709031Z 2026-05-04T23:09:56.730Z �[32minfo�[39m: ➖ Connection (0) 1006 module="websocketMain"
[Homarr] 2026-05-04T23:09:56.762552199Z 2026-05-04T23:09:56.762Z �[32minfo�[39m: SIGTERM module="websocketMain"
[Homarr] 2026-05-04T23:10:17.044295888Z 22:M 04 May 2026 23:10:17.043 * 1 changes in 60 seconds. Saving...
[Homarr] 2026-05-04T23:10:17.044360037Z 22:M 04 May 2026 23:10:17.044 * Background saving started by pid 3509
[Homarr] 2026-05-04T23:10:17.048166356Z 3509:C 04 May 2026 23:10:17.047 * BGSAVE done, 34 keys saved, 0 keys skipped, 29259 bytes written.
[Homarr] 2026-05-04T23:10:17.055130005Z 3509:C 04 May 2026 23:10:17.053 * DB saved on disk
[Homarr] 2026-05-04T23:10:17.055198085Z 3509:C 04 May 2026 23:10:17.054 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
[Homarr] 2026-05-04T23:10:17.145946855Z 22:M 04 May 2026 23:10:17.145 * Background saving terminated with success

Impact

Unfortunately makes Homarr unusable for now.

Additional information

No response

Version

1.60.0

Installation method

Docker Compose

Browser

Brave

[manuel-rw]

What hardware are you using?
SIGTERM is usually sent by the host.

[xiskyliner]

What hardware are you using? SIGTERM is usually sent by the host.

Hey,

im hosting on a UGREEN NAS DXP2800
Intel(R) N100 4Cores
8 GB DDR5 5600 MHz

CPU Load is usually around 40-70% with all Containers up
Same goes for the RAM.

Homarr uses 250-450MB RAM while running.

Thank you for your reply