Search Criteria
Package Details: synology-drive 3.4.0_15724-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/synology-drive.git (read-only, click to copy) |
---|---|
Package Base: | synology-drive |
Description: | Drive for PC, the desktop utility of the DSM add-on package, Drive, allows you to sync and share files owned by you or shared by others between a centralized Synology NAS and multiple client computers. |
Upstream URL: | https://www.synology.com |
Keywords: | synology |
Licenses: | custom |
Submitter: | fmartingr |
Maintainer: | fmartingr |
Last Packager: | fmartingr |
Votes: | 45 |
Popularity: | 0.48 |
First Submitted: | 2018-01-03 10:34 (UTC) |
Last Updated: | 2023-11-09 07:15 (UTC) |
Dependencies (2)
- glibc (glibc-gitAUR, glibc-linux4AUR, glibc-eacAUR)
- nautilus (nautilus-legacyAUR, nautilus-gitAUR, nautilus-typeaheadAUR) (optional) – For nautilus integration
Latest Comments
1 2 3 4 5 6 7 Next › Last »
moabeat commented on 2023-09-13 20:32 (UTC) (edited on 2023-09-13 20:58 (UTC) by moabeat)
While using KDE Plasma 5 and Wayland, I only get these errors now. Any idea how this can be fixed? I think it's just since 1 or 2 days and it was working fine before. Reinstall didn't fix it and Synology also didn't release a newer version.
Edit: Okay, figured this out. Obviously SynologyDrive requires execute permissions on the user's home drive and won't work otherwise. ;-) That's a bit nasty. Had my /home partition mounted with "noexec".
PatronMaster commented on 2023-05-04 12:29 (UTC)
I also installed in Manjaro and worked very well. Thanks :)
Diota commented on 2023-04-26 08:47 (UTC)
I installed it on 4/26 and it works fine on my machine. I dont think it's out of date.
krassecommits commented on 2023-01-02 15:40 (UTC)
Seems like they dumped the i686 build, it even says (64 bits, deb) on the download page. Nevertheless, it would be nice to update this package with the commit from @ThinOrangeHaze
ThinOrangeHaze commented on 2022-12-24 17:01 (UTC)
Patch for new update. Can't find the i686 version of the latest release however.
oysstu commented on 2022-11-25 17:32 (UTC)
The certificate thing seems to be fixed in 3.2.0-13258
Panzki commented on 2022-11-19 09:28 (UTC)
I encountered the same issue, and I was able to resolve it by manually adding the needed root CAs certificate the ~/.SynologyDrive/data/certs.pem file.
I'm using a certificate issued by Let's Encrypt and the root certificate for my certificate was ISRG Root X1. I copied the the root certificate by running:
cat /etc/ca-certificates/extracted/cadir/ISRG_Root_X1.pem > ~/.SynologyDrive/data/certs.pem
After restarting the Synology Drive client HTTPS is working again.
ZEBofx commented on 2022-11-01 20:24 (UTC) (edited on 2022-11-01 20:27 (UTC) by ZEBofx)
I have the same thing : ~/.SynologyDrive/data/certs.pem is empty after the error or after restarting the client. I tried to delete the files, but it recreated it empty.
I just recreated it "by hand" (cat all my CAs > certs.pem), and then "chmod u-w ~/.SynologyDrive/data/certs.pem". Seems to work for now.
fmartingr commented on 2022-11-01 19:53 (UTC) (edited on 2022-11-01 19:57 (UTC) by fmartingr)
I use my linux machine mostly headless now, so I have not been using Synology Drive lately from there. I just upgraded my entire system (including synology drive which is still there) and connected to my synology without problems, using a self-signed certificate but ignoring the warning. Files are syncing both ways just fine. Where are you getting this errors from?
My synology drive server version is 3.0.3-12689.
Edit: ~/.SynologyDrive/data/certs.pem is populated on my case. Maybe deleting it will make the client restore it?
Edit2: Just moved my certs.pem file to somewhere else, closed drive and opening it again create the file again, poppulated.
1 2 3 4 5 6 7 Next › Last »