Hi, I moved this year to another city, because my internet provider didn’t give me a dedicated ipv4 address I can’t use a dyndns like duckdns. Another thing to mention is, that I have a dslite tunnel. So I can’t set up dyndns…
So my recent setup is a truenas server sitting under my desk. This is connected via cloudflared to the cloudflare tunnel. There I have my services like seafile or nextcloud configured. They are all pointing to a traefik instance that routes the traffic to the right container.
So to summarize what I have:
- Truenas server
- multiple services
- dslite tunnel
- own domain
- Cloudflare tunnel
- v-server
- Nginx
- docker
To visualize the route the traffic is going
Internet - cloudflare tunnel - cloudfared docker - traefik docker - service (nextcloud) docker
So I want to setup something on my v-server that routes the traffic to my homeserver (truenas)
Internet - DNS (cloudflare) - v-server - (magic docker service on truenas) - traefik docker - service (nextcloud) docker
Does someone have an idea how to solve this?
I’m in the same boat and looking at options. I’ve benchmarked several options tht provide their own relays, and am in the process of setting up my own relays to test out on oracle free tier vps, which will probably be the best option as all the bandwidth that vps can handle will be dedicated to you and not shared. That said I’ve found tailscale to perform the best and twingate to perform the worst. I’m looking at netbird and netmaker but they’re extremely buggy and difficult to get going. Netbird is just busted in so many ways. Netmaker’s relays can’t get past my cgnat. Self hosting both of these should work but I’ve not tried it yet. The absolute easiest to set up has been tailscale though, can’t go wrong with that. For most use cases except for handling massive amounts of data, tailscale should be more than sufficient. That said, I’m looking to try selfhosting netbird, netmaker and headscale to see how those perform compared to tailscale’s own relays.