Tutorial Share file links 2019-04-20

[Rusty]

Essentially, even this route your public ip could still be found, by pinging the domain name to the Drive destination right?

Ofc. This is not why I'm using a reverse proxy. The fact is that all apps are ending up on my NAS environment. I do run them over cloudflare for added ddos and flood protection. Revers is here just so don't use my ddns name, and the fact that I can add multiple domain names that are covered with my wold card certificate. Also, Synology's LE implementation of LE doesn't support wild card certs, so a private domain is a way for me.

 

[Gerard]

Ofc. This is not why I'm using a reverse proxy. The fact is that all apps are ending up on my NAS environment. I do run them over cloudflare for added ddos and flood protection. Revers is here just so don't use my ddns name, and the fact that I can add multiple domain names that are covered with my wold card certificate. Also, Synology's LE implementation of LE doesn't support wild card certs, so a private domain is a way for me.

What’s the service on cloudflare that you use called?

 

[Rusty]

Nothing special, I just run DNS and http proxy requests over them (CDN)

 

[Imcon]

Hi, back to the Share Links / File Links,
I have a question I'm not able to answer...:

- To connect to our DSM we use port 1234 (f.example), => the address looks like: https://domain.com:1234/
- then to connect to our Office/Drive the address is: https://domain.com:1234/office/
- when we create a File Link from DSM then the link is created via gofile service and it looks like: http://gofile.me/6x7rV/9cmruDsC which is translated to the link: https://domain.com:1234/sharing/9cpouDbC which works fine.

The problem is that when I want to create a Share Link for a document from Drive/Office, the Drive create this kind of link: https://domain.com/office/oo/r/4978316472891600[/URL]- WITHOUT the proper port.
Such link does not work, of course.

I'm not able to figure-out, how to set DSM to create correct Share Link, which should look like: https://domain.com:1234/office/oo/r/4978316472891600

Anyone experienced can help me to set the DSM correctly?
Thank you!

 

[Telos]

I'm not able to figure-out, how to set DSM to create correct Share Link, which should look like: https://domain.com:1234/office/oo/r/4978316472891600

That's odd. Drive share adds the port in my case.

Is 1234 the default https port on your NAS, or are you using your router's to redirect 1234 to 5001? Or reverse proxy?

 

[Imcon]

Thx for the answer,
I probably messed-up something in the DSM setting.
Can you let me know where you have set the port (one which is listed in Drive share because there are many different port settings in the DSM)?

The port 1234 (this is just for the example the real one is different...) is the default port of my NAS set in ControlPanel/Extermnal Access/DSM(HTTPS).

Rourter is set to pass the port 1234 from outside to the 1234 of the DSM.

Peverse Proxy: honestly - I do not know how to use it, therefore it is not set.


Any idea?

 

[Telos]

Any idea?

 

[Imcon]

All right - That is set in my DSM too. So the setting are at two places (I do not understand why there are two different settings for the same thing):

1. ControlPanel/Extermnal Access/DSM(HTTPS)
2. ControlPanel/Network/DSM settings

 

[fredbert]

I've not used sharing that much but I just tested how a link changes if adjusting Drive's Application Portal settings in Control Panel.

I only get a link like https://mydomain.com:secport/.... if I disable all the Application Portal support, meaning: there's no quick access using /office when this is all disabled.

Using the different portal features gets a share link based on either https://mydomain.com/office... or https://office.mydomain.com/...

I don't seem to get it to insert the DSM HTTPS port when app. portal is configured. I do have Web Station running so maybe there's an assumption that the HTTPS/443 connection is available and more likely to be accessible from everywhere.


But I do have DSM HTTPS port and HTTPS/443 both forwarded to my NAS so the links work.

 

[Imcon]

Well if there are standard ports, it works well - no port necessary in the share link.
But as soon as the port is changed (and we use Quick connect too), I do not get the right link with the port.

 

[Telos]

ControlPanel/Extermnal Access/DSM(HTTPS)

I left these blank. They serve no purpose here. You would only fill these in with values different from your standard "1234".

I've not used sharing that much but I just tested how a link changes if adjusting Drive's Application Portal settings in Control Panel.

FWIW, I'm not using this w/Drive. It IS the alias that causes the port issue. Another buggy issue for
"non-standard" port use that Synology ignores.

 

[fredbert]

I think I've figured it out...

Synology Drive Admin Console / Settings / Others ... scroll down to Customize Sharing Link and you can set what you want here, even a customised one.

So you can make your sharing link by explicitly setting https://domain.com:1234/office/ as the customised domain.

 

[jeyare]

everything works perfectly by reverse proxy, then no needed ports

 

[Telos]

everything works perfectly by reverse proxy, then no needed ports

Doesn't reverse proxy in this case, defeat the reason we use custom ports... to avoid script kiddie attempts.

 

[jeyare]

Doesn't reverse proxy in this case, defeat the reason we use custom ports... to avoid script kiddie attempts.

sorry for my distraction, lost Imcon’s request

 

[Imcon]

I think I've figured it out...

Synology Drive Admin Console / Settings / Others ... scroll down to Customize Sharing Link and you can set what you want here, even a customised one.

So you can make your sharing link by explicitly setting https://domain.com:1234/office/ as the customised domain.

Thanks!
That was exactly what I was lookig for. Using Synology more then 10 years, but still something to learn...

PS: a great forum here.