In /etc/hosts define a new host providing “IP FQDN”. LinkStation 200 runs on Buffalos LinkStation NAS System.
To resolve FQDN to a private IP, for some reason Synology does not send a private Ip. I can connect to the Synology home page using a browser on the phone so network connectivity is OK. The SSL certificate should now be trusted. After few minutes, your FQDN is linked to that Ip and can be verified on Synology Account website.
#Synology drive client connection failed update
Go to External Access, DDNS, Edit, and update the IP address for your domain name FQDN.
Also, turned https on and off with no effect. I removed all trusted connections and started again. It’s only the upload part in Drive in phone app. Synology drive client on laptop also works with that certificate. So, to see the status in real time you need to monitor the Synology Service Status page, but be careful: even if the page should be monitoring the situation in real time, it’s actually not real time. There is no problem with upload download from DSM web browser. SOLUTION 1 Synology Server Problems: Most of the time the problem is attributable to issues on Synology servers. I updated the certificate on NAS which is valid til next year. I receive an upload fail error, with a message somewhere that SSL certificate is not trusted.Īll devices (NAS, phone and laptop) are connected to a VPN concentrator server. From phone I can only download but not upload. From laptop I can download and upload files and I see them on NAS. But when using listen 6690 ssl the Synology Drive Client cannot find the NAS, and when using listen 6690 (without SSL) the NAS is found, but its unsigned certificate is used instead of the certificate stored with nginx. I have synology drive client apps on my phone and laptop connected to NAS. 0 tl dr I tried setting up nginx to forward a TCP connection over 6690 to Synology Drive.
0 kommentar(er)
