server {
listen 80; # listens only on IPv4 port 80
server_name example.com; # your domain name
location / {
proxy_pass http://[2a03:2880:f003:c07:face:b00c::2] # replace with your home server IPv6. Keep the brackets.
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_redirect off;
}
}
Point your A record to your VPS, and your AAAA to the home server.
Be careful with doing this. X-Real-IP and X-Forwarded-For are good for when the client is a trusted proxy, but can be easily faked if you don't whitelist who's allowed to use those headers. Somebody with IPv6 access could send "X-Real-IP: 127.0.0.1" or something and if the server believes it then you'll see 127.0.0.1 in logs and depending on what you're running the user may gain special permissions.
Also be careful with the opposite problem. If your server doesn't trust the proxy, it will show the VPS IP in logs, and if you're running something like fail2ban you'll end up blocking your VPS and then nobody will be able to connect over IPv4.
Probably overkill, but for projects like this I've setup WordPress in the past. Once everything was done, I converted the WordPress page to a static site with httrack and use the static version.
This gives the ease of setting up and editing combined with the stability and security of a static HTML website.
While you can probably use them for some small tasks (like a switch, a file server with a USB thumb drive or a print server), you're probably better off if you can sell them and buy a raspberry pi or similar.
The Fritzbox 7530 for example could be sold for 50€ (at least in my country).
Tailscale is an overlay network. It will use whatever networking is available. If only one of those NICs is a gateway, then that’s what will be used to reach remote Tailnet resources.
Router like this are very low spec for example Fritz!Box 3270 has 360 MHz 1 core CPU, 64 Mb of RAM and 16 Mb of Flash. Only thing you can do with them is flashing OpenWrt, but its latest version doesn't support devices with or less than 8 Mb of flash and 64 Mb of RAM.
You want OpenWRT. They're not too limited, but they're not very powerful either. Fan controller? Probably. Pihole? You can probably hack that together, though I've never tried. Media server? Erm... not my first choice. Other stuff? Limited only by your imagination, time constraints and willingness to troubleshoot weird problems most people have never had before.
I also put a few Braille dots on few buttons and glow in the dark paint on a few important dots to make it more usable which really works, Braille especially.
Then... A few bookmarks in the firefox, jellyfin, navidrome, Spotify, vlc/MPV from mounted NAS etc.
I don't bother with any media/apps interface, I mostly see them as annoying and not needed with this KB/trackball setup.
I have a very similar setup like you. A NUC is providing NAS functionality and is running 24/7. An AppleTV is connected to the projector and has all the apps I need for consuming media (Jellyfin, Netflix, etc.). The NAS is running OG Debian with SMB, Jellyfin and even NFS for easy access.
The NUC provides additional features like synching and a few other things.
Why the AppleTV? Because I had Raspis, FireTVs, PCs, and whatnot connected to the projector and the AppleTV is hands down the most convenient one. The UI is super reduced and simple. The remote works. You can get just about every app you might need. And maintainance is basically zero.
Just external - I know it's not the best solution. My setup grew on a tight budget over the last 10 years and for me it was the easiest, most affordable, and extendable/replaceable way. I don't need super fast drives in my home and I don't need backups for most of the data stored on a media server. So it kind of is just a bunch of disks with a NUC.
The internal drive for the system is an SSD though. Came with the computer.
I do it like that.
8TB external drive on an 11th i5 gen nuc.
Almost every service is dockerized because I can't be bothered to manage the dependencies.
Selfhosted
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.