Selfhosted

40347 readers

393 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

[Tailscale] Can't connect VPS to local network? (lemmy.dbzer0.com)

submitted 7 months ago by dataprolet@lemmy.dbzer0.com to c/selfhosted@lemmy.world

30 comments fedilink hide all child comments

I set up Headscale and Tailscale using Docker on a VPS, which I want to use as my public IPv4 and Reverse Proxy to route incoming traffic to my local network and e. g. my home server. I also set up Tailscale using Docker on my home server and connected both to my Headscale server.
I am able to ping on Tailscale container from the other and vice versa and set up --advertise-routes=192.168.178.0/24 on my home server as well as --accept-routes on my VPS, but I can't ping local IP addresses from my VPS. What am I missing?
Both container are connected to the host network, I have opened UDP ports 41641 and 3478 on my VPS.

you are viewing a single comment's thread
view the rest of the comments

[–] dataprolet@lemmy.dbzer0.com 1 points 7 months ago (6 children)

Of what?

[–] riffy@lemm.ee 3 points 7 months ago (5 children)

image: tailscale/tailscale:v1.60.1

To pull that version of tailscale. Latest broke subnets.

[–] dataprolet@lemmy.dbzer0.com 1 points 7 months ago (4 children)

Doesn't seem to work.

[–] riffy@lemm.ee 2 points 7 months ago (1 children)

You might have other issues then, but I'd use that version of tailscale since it was the last version to work with subnets. Also, only the owner's account works cuz sharing subnets broke even longer ago, and I'm positive neither has been fixed. Good luck!

[–] lemmyvore@feddit.nl 2 points 7 months ago (1 children)

Subnets seem to work for me with 1.62.0 docker image. In what way were they broken?

[–] riffy@lemm.ee 2 points 7 months ago* (last edited 7 months ago) (1 children)

I reported it the day the update was released cuz all of my containers are on their own ip. Got that update and nothing was reachable till I rolled back.

GitHub

load more comments (2 replies)