app not showing correct info on synology NAS

[carloscarotaa-coder]

Describe the bug
it proceeds to only show 100% used of 1024b and no cpu usage or system info, ssh still works
i am connecting over tailscale

To Reproduce

Desired Results
showing correct system info and syste resources usage

Actual Results
showiing incorrect info and no usage

Screenshots

Device

Additional context

[GT-610]

When ServerBox fails to fetch these data it will just show like this.

Since I don’t have a Synology device, I may not be able to resolve this issue right away. However, we have already begun investigating the cause.

[GT-610]

Thanks for the report. We have investigated the screenshots further.

The 100% of 1024 B value is not the actual memory size of the NAS. It is a fallback value shown when ServerBox does not receive or recognize the memory information. The missing CPU, system, and disk I/O data also indicate that the monitoring script did not return all expected sections, even though the SSH connection itself succeeded.

Since this issue was reported, we have fixed several related problems, including handling the Could not chdir to home directory warning commonly seen on NAS systems. These fixes are included in ServerBox v1.0.1480.

Could you please update to v1.0.1480 or newer and check whether the issue still occurs?

If it still happens, please provide:

1. Your Synology model and DSM version.
2. The ServerBox logs immediately after connecting. Please copy the full error details if possible.
3. Whether the logs contain any of the following messages:
   • Could not chdir to home directory
   • Empty response from server
   • Unsupported script output protocol
   • Script installation exited with code
4. The output of these read-only commands when run through SSH:

uname -a
pwd
echo "$HOME"
cat /proc/meminfo | grep -E 'Mem|Swap'
cat /proc/stat | grep '^cpu'
cat /etc/*-release | grep '^PRETTY_NAME'

Please redact any usernames, hostnames, or other private information before posting the output.

Tailscale is unlikely to be the direct cause because the SSH connection is working, but the additional information above should help us determine whether this is a Synology shell compatibility, permissions, or script-output parsing issue.

Thanks for helping us investigate this without direct access to a Synology device.