Comment

Comment on connection/certificate errors from DSM. Package center, QC, and much more unavailable.

sfcl33t@discuss.tchncs.de ⁨1⁩ ⁨year⁩ ago

Sorry you’re going through that OP. I manage around a dozen large business Synology servers, and this right here is why I cringe when I see it be so often recommended for home use. I appreciate the value they bring for home labs with all their out of the box bells and whistles, but when they fail, they fail really hard.

For your use case, your best bet is to ssh in and start digging through the logs. You’ll be missing a lot of basic tools when you ssh in, like a text editor, and there is probably no package manager to install anything from the shell. I remember last time I had to do that I had to install some stuff by downloading directly. I believe I was also able to mount a remote drive from the shell and copy the logs over at one point.

Anyway, the log files should at least give you plenty of error messages and at least point you in the right direction for working with support. Good luck.

source

Sort:hotnew top

MonkCanatella@sh.itjust.works ⁨1⁩ ⁨year⁩ ago
I found something that says

Failed to exec curl command, with url: https://update7.synology.com/autoupdate/v2/getList , with reason: error setting certificate file: /etc/ssl/certs/ca-certificates.crt

I SSHed into /etc/ssl/certs and that doesn’t exist. What does exist is a bunch of files like “b23h893.0” "“fb3j58d.0”, etc. using ls -l I see that they have lrwxrwxrwx permissions on all of them and they point to stuff like affirmtrust, comodo cert, amazon_root, etc. nothing that makes any sense to me.

checking certificates from the control panel, all certificates are assigened to the cert generated by my quick connect url. I have 3 in total, one with my quick connect url, one with .direct.synology.me, and and that’s just ‘synology’. They all have a lock with a green checkmark, assuming that means they’re legit but idk. What may be causing issues is that I can’t use my quick connect. It’s glitchy - I can’t enable it because I get a connection error, but I’m wondering if that’s cause of some certificate or maybe it’s due to the error I showed above - that setting up the quick connect is throwing an error because it wants to write to some certificate that doesn’t exist.

source
MonkCanatella@sh.itjust.works ⁨1⁩ ⁨year⁩ ago
I checked out log center and there wasn’t nearly enough information in those logs. Where would I find

FYI I can still access the DSM interface, but it gives errors on lots of things that I know need to get sorted. I will look into the logs. Do you have any pointers on what I might want to check for, or ways I could ensure I’m not compromised in any way? You mentioned you fixed yours by downloading some stuff directly, do you happen to remember more about that? I really appreciate the help and the sympathy. I seriously couldn’t sleep the night it happened purely out of stress/anxiety :/

source