Win/Mac Synology Drive Client unable to connect with domain

Currently reading
Win/Mac Synology Drive Client unable to connect with domain

101
36
NAS
DS923+
Operating system
  1. Linux
  2. macOS
Mobile operating system
  1. Android
Hello all!
I think that another user had the same issue with me a few months ago, but unfortunately search did not help to locate any relative thread. Forgive me if it was discussed again, please in such case just redirect me to have a look...

So, I have installed and configured Drive Server. In Control Panel --> Login Portal --> Applications I have set a domain drive.xxxxxx.synology.me for Synology Drive. Of course port 443 is allowed in firewall rules and port 443 also forwarded from the router, I use reverse proxy a lot.
All my mobile devices (Android) with Drive app can connect to the above domain with no issues at all. Mac and windows systems can only connect if I use the local IP and the connection cannot be established if the domain is used.
What could be the problem? Are there any additional ports I should allow/forward? Why is this happening for Win/MacOS but Android Drive app works just fine?

I know I could use QuickConnect instead (tested and works) but I would prefer to avoid enabling it.

Thank you in advance...
 
Solution
Finally found some info on this thread.
So, to my understanding, it is impossible to use win/mac Drive clients through reverse proxy.

Since my laptop is a Mac, I ended up connecting and mounting volumes from "Connect to Server" option of MacOS, pointing to my Drive destination folder. That workaround works OK with WebDAV.

Finally, also tested Cyberduck (great tool, was using it only for ftp/sftp till now) and Mountain Duck (suits great my needs and I bought a license to use it as my default tool for such cases).

I put this info here just in case anyone else has the same question in the future...
Finally found some info on this thread.
So, to my understanding, it is impossible to use win/mac Drive clients through reverse proxy.

Since my laptop is a Mac, I ended up connecting and mounting volumes from "Connect to Server" option of MacOS, pointing to my Drive destination folder. That workaround works OK with WebDAV.

Finally, also tested Cyberduck (great tool, was using it only for ftp/sftp till now) and Mountain Duck (suits great my needs and I bought a license to use it as my default tool for such cases).

I put this info here just in case anyone else has the same question in the future...
 
Upvote 0
Solution

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Similar threads

I have Synology Drive Client installed on a Win10Pro box. I've set up my Calibre library as a one-way...
Replies
0
Views
1,689
So as I found no way to fix things, I deleted the shared NTFS partition and all synology drive sync...
Replies
10
Views
8,813
I managed to nuke the Drive client install by just deleting all folders and hidden files I could find...
Replies
7
Views
4,229
SOLVED It was, in face, the precious few 15 overlay slots allowed by Windows. I had installed something...
Replies
1
Views
499
1.) Python is the way: #%% import os from re import U, purge from dirsync import sync #%% #Task1...
Replies
1
Views
555
Thank you, that will help, but its almost there. Not all places I support use AD or even LDAP. I would...
Replies
2
Views
540

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Trending threads

Back
Top