Comment on Help Wanted: Accessing a Service With the Same FQDN Inside and Outside Local Network
dan@upvote.au 3 days ago
Use Unraid’s native Tailscale support. Add each Docker container to the Tailnet. The Tailscale IPs will work both on and off your LAN, as long as you’re connected to Tailscale. Don’t use a subnet router. Tailscale is peer-to-peer, so it’s still going to connect directly over your LAN when possible.
For TLS, you could use the Tailscale built-in .ts.net subdomains. Should work out-of-the-box. Otherwise, to use your own domain, f you can’t get access to Namecheap’s API you could run acme-dns instead.
iamthetot@piefed.ca 3 days ago
Would this method allow other people to connect to one of the services? Let’s say, for sake of example, it’s a blog that I want people to be able to access, but I also want to access from within my own network at the same FQDN that strangers on the internet do.
dan@upvote.au 3 days ago
If you want to share something with just some people, they can create a Tailscale account and you can share it with them that way.
For public access, accessing it using a domain that uses your public IP should work. Most routers let you do that (“hairpin NAT”). Although to be honest, most of my public facing things are on a VPS rather than on my home server. More reliable and a higher quality internet connection for a fairly cheap price per month.
iamthetot@piefed.ca 3 days ago
Outsiders accessing all the services via tailscale is not an acceptable solution for me. Let’s say for sake of my goal that one service is a blog that I want anyone to be able to reach.