High CPU usage and app unresponsive on Synology

[Wombat]

Hello, I just bought Syncovery and installed it on a Synology 1819+ with 32GB of RAM. Syncovery is generally unresponsive and is taking up excessive amounts of CPU. Originally it seemed OK because I was able to register it and also update the SSL certificate but now it basically doesn't load at all.

Screenshot 2025-07-15 175329.png (57.66 KiB) Viewed 41 times

I've tried the version that runs as user Syncovery and also the version that runs as root. No difference. I tried reinstalling Syncovery, and also clearing out the residual configuration files and nothing seems to help. Happy to send any log files if needed. Thank you.

[tobias]

Hello,
thanks for the report. Do you have the latest version 11.6.1?

There are some ways to analyze this. If you like you can call us or write to support@syncovery.com and we can do a remote session, such as via TeamViewer, to work on the problem.

Maybe it's having a problem with the SSL configuration. If you're in a LAN exclusively and don't open the Syncovery port to the Internet, you might not need it.

You could collect some log files from the Syncovery folders, such as /volume1/@appdata/Syncovery/Logs, but these can be hard to actually extract out of the Synology device.

Additional logs are one level further up, in /volume1/@appdata/Syncovery, especially WebGUI.log.

A way to get a detailed report on what Syncovery is doing or where it's hanging is this:
cd /var/packages/Syncovery/target/usr/bin
touch wantstatus
and then wait a few seconds for an activity report to appear in the same folder.

What we could do is stop the Syncovery service, remove all config files, and restart it so you can start fresh. Then maybe work without SSL for a while just so we can see if that was the cause.

If you want to try this, you'd do
sudo killall -9 SyncoveryCL
cd /volume1/@appdata/Syncovery
mkdir prev
sudo mv * prev

But make sure it successfully changed into the Syncovery folder before entering the last command!

And then you need to reinstall the latest Syncovery version so that the web server is set up again and the basic configuration is written.

[tobias]

Hi,
just in case you're already trying things: I updated the instructions on how to restart Syncovery after moving the confuration files away.

The only way is actually to reinstall the latest Syncovery version so that the web server is set up again and the basic configuration is written.

[Wombat]

Hi Tobias, it definitely seems to be related to configuring ssl. A new install with no ssl works perfectly. Configure ssl and the problem appears. I need to experiment a bit more but I think it happens both with my own certificate and one generated by Syncovery. This is only happening on Synology. On Asustor it is fine.

I am on the latest version, downloaded today.

Edit: What does seem to work is using the Synology certificate from the nas /usr/syno/etc/certificate/system/default/RSA-fullchain.pem and accessing Syncovery using https://nas-name:8999. If I try and use my own wildcard certificate for *.home.lan then Syncovery doesn't seem to like this at all. This same certificate is being used in many places without a problem and as mentioned, it is perfectly OK on Asustor. Also I get the problem with the certificate generated by Syncovery. So I am puzzled.

[tobias]

Thanks! I will make some tests here. I haven't generated new certificates in a while but the old ones I have work fine.

I have also released version 11.6.3 just now with a few minor improvements.