Selfhosted
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.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
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!
view the rest of the comments
Adguard home has a DNS rewrite function that you can use to rewrite local DNS queries.
I use it to rewrite my queries at home to point to the LAN IP. When I am out I get my public IP from normal resolvers.
So you have a public DNS record pointing to your home IP?
DNS server you use from your home network retuns 192.168.1.20 for your service hosted at jellyfin.Bob.org
The DNS server you hit when publically looks up jellyfin.Bob.org and gets the IP from the nameserver you have set with your domain registrar often just theirs and you set this to your home WAN ip.
You have to configure both. I use opentofu / terraform to configure both all from the CLI. Any software like DNS that has a bunch of implementations that doesn't have Open-Tofu support gets skipped and an alternative is found at this stage. You just can't beat config as code for this type of set up.
You can also use NAT reflection which will effectively reroute the connection from within your network to your external IP to work on your local network.
I started with reflection and ended up going to the multiple DNS servers as it felt cleaner and I already was running Adguard so why not.
Both adguard and pihlle have opentofu modules.
Rereading your post (heh): In your case I'd just always serve over the wireguard ip local or not. Why do you want to use the local IP vs wireguard? The overhead of wireguard is pretty low
Oh hm I didn't think about your last point, maybe it's not really an issue at all. I think I'm not 100% on how the wireguard networking works.
Suppose I tunnel all of my traffic through wireguard on the remote server. Say that while I am home, I request
foo.local, which on the remote server DNS maps to a wireguard address corresponding to my home machine. The remote will return to me the wireguard address corresponding to the home machine, and then I will try and go to that wireguard address. Will the home router recognize that that wireguard address is local and not send it out to the remote server?Your home router knows nothing about your wireguard VPN unless it is also configured to be a peer in it. So in short no it will not recognize and route your connection locally unfortunately.
Are you using TLS here at all? Can you give me an example of how you access this on your phone when remote vs when local.
e. g. From my phone on cellular I go to Firefox and type in jelly.bob.com which resolves to my wireguard ip hitting the VM in the cloud that then using nginx as a reverse proxy to reach jellyfin over my network.
Remote network: jellyfin.bob.com Phone - > VM - > Home Server where Jellyfin is running
Is each hop is over wireguard i.e from phone to VM from VM to Home Server?
On the local network: jellyfin.bob.com Currently looks the same as the above and what youx like it to do with the same name is go: Phone->Home server
Even when wireguard is on, correct?
Yes your description is just right and is the heart of my question. To use your terminology:
Currently:
Ideally:
In the ideal case, I would never have to change anything about the wireguard config/status on the Phone, nor would I have to change the domain name used to reach the resource on the Home Server.
Are you routing DNS over wireguard the whole time or do the DNS servers change when you go from public internet to your home network?
If you are using the same DNS servers i.e. always using DNS over wireguard then there isn't really a lot you can do.
The way I do this is when I am on my home network I use the DNS on that network, i.e. the adguard instance I set up and also override DNS names with, when I am on some public internet i.e. via cellular, I use whatever DNS server they have. So on home network jellyfin.bob.com returns 192.168.8.3 (for example) and on the public internet jellyfin.bob.com will return 68.32.23.11 (i.e. my public IP address).
However that requires multiple DNS servers.
What is an example server where you'd like to do this (it may give us more options) and how is your DNS set up?