Looking into OpenCloud and just wondering if anyone's got it working with Tailscale via TSDProxy?

[nefariouslegion]

Hi,
Currently I use TSDProxy on most of my containers to make them accessible remotely over the Tailscale network. For most containers it's as simple as just adding a few "labels:" lines to the docker compose file. Then the container's service becomes accessible using the container's Tailscale URL. I currently use this and do not own an actual domain.

So I'm wondering if it's possible to do this with OpenCloud? I tried searching but haven't found any information on whether or not this would work.

The other thing is I do know when I look at the OpenCloud Docker Compose guide the first thing it mentions is needing 4 domains. But would it be possible to substitute domain names with a Tailscale URL for each service?

TIA for any advice and help!

[micbar]

@nefariouslegion
We did not test that scenario so far.

Some tips: All domains need to be reachable from the outside world and from within the opencloud docker container. As long as that is guaranteed, this should work.

[nefariouslegion]

Thanks for the reply! It’s alright though I ended up buying a domain recently anyways. Just gotta find time to setup OpenCloud

…

________________________________ From: Michael Barz ***@***.***> Sent: Monday, October 13, 2025 2:52:47 AM To: opencloud-eu/opencloud ***@***.***> Cc: nefariouslegion ***@***.***>; Mention ***@***.***> Subject: Re: [opencloud-eu/opencloud] Looking into OpenCloud and just wondering if anyone's got it working with Tailscale via TSDProxy? (Discussion #1647) @nefariouslegion<https://github.com/nefariouslegion> We did not test that scenario so far. Some tips: All domains need to be reachable from the outside world and from within the opencloud docker container. As long as that is guaranteed, this should work. — Reply to this email directly, view it on GitHub<#1647 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AVJ2BE7UMV2YUKS2GX2RP6T3XND37AVCNFSM6AAAAACI5NI73SVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINRWGI2DIMI>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[flimmy]

see #1903 (comment)