When I am on the new sparkbox hompage there is no warning, on the classic hompage it gives me a warning : 1 service needs attention
11 replies
Chris wrote:
I can see the mismatch: the new homepage shows no warning, while Classic says one service needs attention. What SparkBox version are you running, and which app (if any) does Classic identify as needing attention? Please share just those details—no logs or passwords—and I can narrow down whether the two homepages are reporting the same service differently.
franciscus wrote:
I asked tom already, 5 times, same result. He did doctor, logs, the whole shebang. Nothing to find.
Chris wrote:
I’m sorry you’ve been sent through Doctor and log checks repeatedly without getting an answer—that’s frustrating, and I won’t ask you to run them again. I can’t tell from here why the two homepages disagree; the latest information I have doesn’t confirm a fix for this exact mismatch. One useful detail, if you have it handy: what app does Classic name as needing attention (or does it name none)?
franciscus wrote:
uptime-kuma I deletet it after nothing worked and installed it again, same : 1 service needs attention
Chris wrote:
I’m sorry you were sent through Doctor and log checks repeatedly, and that removing and reinstalling Uptime Kuma left the same warning. Please don’t repeat those steps. Tom is SparkBox’s CEO and doesn’t work the support queue himself; Chris and Anthony are his support team and handle support end to end, and anything that genuinely needs Tom’s decision is escalated to him with a durable record. One read-only check: on the newer dashboard, what status label does the Uptime Kuma tile show?
franciscus wrote:
All green, and I can open the app, it is normal no problems. The refreshed the classic homepage multiple times too.
Chris wrote:
Thanks, that confirms Uptime Kuma itself is running normally; the newer dashboard and Classic are disagreeing about its status, and refreshing Classic or reinstalling the app hasn’t cleared it. I’ve recorded this specific mismatch so it can be checked rather than asking you to repeat those steps. One useful detail, if it’s visible without running more checks: does Classic name Uptime Kuma next to the warning, or does it only show the count?
franciscus wrote:
The warning for uptime-kuma is gone. I shut down my nas because I changes something in my rack. After an hour my nas was up again and now cloudflare crashed. I runned "sudo sparkbox up" ( I did several times while the warning showed, doctor too) and now warning is gone, from uptime-kuma too. The problem solved after an total shutdown en then restart, instead of just restart.
Chris wrote:
Thanks for the update—good to hear the Classic warning cleared after the full NAS shutdown and restart. That confirms the warning cleared, but not why it appeared; the Cloudflare crash may be related, though I can’t confirm that from this alone. Is Cloudflare working normally now as well?
franciscus wrote:
Working: All checks passed!
Chris wrote:
Great, thanks for confirming Cloudflare is working and all checks pass now. I’m glad the warning cleared after the full NAS shutdown and restart. We still can’t tell what caused the warning, so there’s no need to repeat the shutdown or reinstall while everything is working.