Neat visuals but I don't think this is in any way accurate... Tell me how I crossed all those lightyears in about 60 seconds while only traveling at around 95% the speed of light.
stown
joined 10 months ago
You can do this with a site-to-site wireguard VPN. You will need to set up the proper routing rules on each termination. On the Internet facing side you will want to do DNAT (modifies destination, keeps source) to redirect the incoming traffic to your non- internet facing side through the tunnel. Then on the non- internet facing you need to set up Routing rules to ensure all traffic headed for public IPs is traversing the tunnel. Then back on the Internet facing side you need to SNAT (modify source, keep destination) the traffic coming through the tunnel headed for the Internet. Hopefully this helps. People saying this goes against standards are not really correct as this is a great application for NAT.
Maybe not the lowest power possible... I wouldn't recommend running your NAS on a raspberry pi even though plenty of people do
I've got a 3800x that has plenty of performance but also uses a lot of power and I'm seriously considering upgrading to a 5700G. It's about 170 from Amazon right now.
Also, I don't think you're going to want your NAS to sleep/standby, that's really not typical.
I wonder if this is the cause for the UI failing and showing a white page with "server error". It has something to do with a failure to retrieve the site icon and if postgres is crashing that could explain why lemmy-ui is failing to retrieve the site icon.
My current "fix" for this is a script that runs every 10 minutes and sets the site image to NULL, curls the site URL, then sets the site image back to what it was. This does seem to work around the problem and if the UI does crash it's only down for a maximum of 10 minutes.
Very nice walkthrough. Gonna bookmark this.
Some of the alternative web-UIs let you do that. Photon for sure and I think Alexandrite as well.
Port 8080 is where the Web-UI / Web-API is running. If you want to be able to upload data and not just leech you need to forward port 6881 (and probably also tell QBT to listen on that port)
Since 0 comes before 1 you're probably gonna need to rename the files and possibly the metadata as well. Probably gonna need a custom numbering scheme to do what you want to do.
Well, you don't have that many brain cells in the areas people are doing that thinking.
When you get a 502 it usually means that your reverse proxy is unable to connect to your backend server. I'm not sure if you've obfuscated the URL in your post but 0.0.0.0 is not a valid IP (it just means ALL IPs). If you are attempting to connect on the same machine that is hosting use 127.0.0.1. if you are on the same network then use the local IP.