I have a VPS (Debian) server for my website and wanna make it useful to make my HA Backups on this VPS. I don’t wanna open the Samba port for the world.
I tried to install Tailscale Addon and then connect to the Tailscale IP number that was given for my VPS. But it won’t connect.
Same idea work to connect from VPS to my NAS at home without issues.
I have similar problem. I want to connect my HA from location A to my network share on NAS at location B and with tailscale it is not working But i managed to connect HA from location B to NAS from location B, so apparently network share is working.
I think I’ve found at least a few breadcrumbs about why this isn’t working; I’ll write those down here, and then look into filing a bug.
The short version is, the Samba addon only listens on specific network interfaces. That configuration is hardcoded into it, and can’t be changed via addon config.
The longer version is:
the Samba addon is configured, presumably for security reasons, to only listen on named interfaces
the interfaces it will listen on are the ones that are returned by the supervisor /network/info API
/network/info at least for me, includes wlan0 and end0, but crucially does not include tailscale0
So, I suspect that the fix is one of three things:
modify the samba addon to allow it to be configured to listen on all interfaces, not just named ones.
modify the samba addon to allow manually specifying additional interfaces to listen on
modify the supervisor API so that it returns the tailscale interface in its network info
(3) is not in scope for me, but I’ll open an HA feature request for it
(1) and (2) require a fork of the addon, or changes to the addon. (1) is the easiest to do, (2) is a safer, but more power-user thing, that requires a user to know their way around the HAOS and be able to see network interface names, which I don’t think is right for most people.