• Hello Guest! SynoForum.com is celebrating its 5th anniversary! 🥳🎉 Read more...

Solved Drive destkop client problem

Currently reading
Solved Drive destkop client problem

Hey there
I used nextcloud for quite a while. But i keep having some issues with external storage. Also I do not like the fact with the docker container not supporting th PUID feature...
Anyway i want to give synology drive a chance to prove itself.
I configured it with following parameters:
So far so good. Then I wanted to test this configuration: Opened the drive app on my iPhone: secret.com, user and password and use https check. And it worked perfect.
And now my struggle: This do not want to work on my computers. Inside the network or outside the network. Always the error: cannot connect to server.
I tried several diffrent option: customise word like secret.com/drive etc. No connection.
I tried it with three macs and a windows virtual machine.
I can only get a connection, when I use the direct IP-address of the server. When I connected with the direct IP I can use the forwarding of the client app to open the drive app in my browser. This is working.
For now... I do not have any addtional ideas.

Is there something I missed? Maybe a configuration? A hidden secret?

Thanks in advance!
That is maybe a good hint. 6690 is a port I'm not aware of.
But then there should be a difference in the mobile and desktop version. The clients will use different ports.

I will check that!
Last edited:
It was the port 6690 :)
Thanks Rusty!
Hi, I just have the same issue, but I don't have clear how to resolve. I redirected on my router the port 6690 to 443 for the reverse proxy do the work.
Here the RP resends from 443 to web interface drive port that I think that is not the way. (it works on browser perfectly).

But I think I missing something.

I just deactivated the firewall on the NAS. No good results.
I tried on synology drive desktop client to connect to drive.mydomain.com and mydomain.com and nothing. "Connection error".

for RP I have htaccess file like this.. for when I becomes an https petition... but it is for HTTP incoming calls redirect https calls.
I start thinking that it gonna be one rule I have that is MyDomain.com redirects directly to DSM Web interface, but it only answer if port is 443, not 6690...

RewriteEngine on
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}

maybe it is redirecting to nowhere the 6690 over ssl?

Can you tell me how do you did that works?


  • Captura.PNG
    26.6 KB · Views: 95
Ok I solved. just using my drive.domain.com and redirect from 6690 to 6690 on router to the nas.
6690 is the Druve client port that desktop and especially mobiles apps use. Apart from that you can get to the drive ui via 443 but the client one needs 6690 to work.

Glad you got it going.

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

  • Question
Following thread too as 6 months ago I removed it on one NAS, and had no issues?
Using Drive Client 3.4.0 on Win 10. By default, it seems like the client is copying my entire home profile...
I found a way to revert syncing the entire Home folders, back to only syncing the Drive subfolder...
The person abroad still get's the same error. I on the other hand have 0 issues connecting through...
I have Synology Drive 3.4.0 installed on a ds223j, and the 3.4.0 client on my MacBook Pro, running Sonoma...
I set up Drive to sync all folders under "My Documents" on windows 10 machine and access them on my...
  • Question
Thanks for your replies. fredbert's suggestion would work I guess, but the folders wouldn't be in my home...

Welcome to SynoForum.com!

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

Registration is free, easy and fast!