Messages

Port 6690 is a pure TCP port for a Synology-specific cloud service, not HTTP(S).

So you are out of luck for using anything that acts name-based like HAproxy, Caddy and so on. While you could use a TCP reverse proxy, that can only be used to change the source port. If the clients cannot make use of another port, you are at an end here, because the only thing that differentiates two devices then is their IP address.

The only way to expose both devices over an internet connection with only one public IP is a VPN, e.g. wireguard.
In that case, you can access both devices by their respective IPs, using the same port.

Thanks, that confirms what I already thought. 😅
I hope Synology let's me change the port somehow. Thanks for the advice! VPN might be the solution.

Hi janiswolf.
you can publish different external ports with NAT.

external_address:1066 --> internal_nas1:6690
external_address:1090 --> internal_nas2:6690

that would work, but synology does not allow me to change the port (client and server side) :-(

Hi

I'm also looking for a solution to this problem.

Synology Drive uses TCP Port 6690 (which cannot be changed). And with two NAS's I cannot access both systems.

Did you manage to find a solution that work for you?

[none]

This configuration works for me with os-ddclient (1.21_2):

Service: custom
Protocol: none
Server: infomaniak.com
Username: ***
Password: ***
Hostname: subdomain.example.com
Check Ip method: ip4only.me
Interface to monitor: WAN INTERFACE
Check ip timeout: 10
Force SSL: Checked

Hope that helps :-)

---

UPDATE: Weird, but I added a second custom service (also infomaniak) in opnsense, and it stopped working. I changed the Protocol form none to DynDNS 2 and now its working again... Weird.