You should take notes about how you set up each app. I have a directory for each self hosted app, and I include a README.md that includes stuff like links to repos and tutorials, lists of nuances of the setup, itemized lists of things that I’d like to do with it in the future, and any shortcomings it has for my purposes. Of course I also include build scripts so I can just “make bounce” and the software starts up without me having to remember all the app-specific commands and configs.

If a tutorial gets you 95% of the way, and you manage to get the other 5% on your own, write down that info. Future you will be thankful. If not, write a section called “up next” that details where you’re running into challenges and need to make improvements.

I also recommend Beelink. I’ve been running an eqr6 (ryzen) for almost a year and it’s been awesome.

Maybe I’m overlooking a lot of circumstances that I haven’t encountered. Good call on the open port feature, that’s a big one that I forgot about.

Seriously. I was recently wondering why so many choose tailscale over WireGuard.

deleted by creator

https://pages.cloudflare.com/

https://docs.gitlab.com/user/project/pages/

I’m also interested. I migrated from mint to Credit Karma… what a complete shit show. I really miss ooold mint.

deleted by creator

deleted by creator

deleted by creator

I don’t think iOS allows multiple VPNs to be enabled simultaneously. There appears to be only one VPN on/off toggle switch. From what I’ve seen you can have different vpn profiles but only enable one at a time. I could be wrong though.

Desktop operating systems like macOS, Linux (did I mention yet that I use arch Linux?), BSD, and um… that other one… oh yeah, Windows do allow this. I’m sure there are a variety of compatibility problems, but in general, multiple VPNs with the same or even different technologies can work together.

WireGuard routes certain traffic from the client (your iPhone) through the server (the computer at your house). If you route all traffic, then when your iPhone accesses the internet, it’s as if you were at home. Since that WireGuard server is sitting on your home LAN, it is able to route your phones traffic to anything else on that LAN, or out to the internet.

Wireguard clients have a setting called AllowedIPs that tells the client what IP subnets to route through the server. By default this is 0.0.0.0/0, ::/0, which means “all ipv4 and all ipv6 traffic”. But If all you want to access are services on your home LAN, then you change that to 192.168.0.0/24 or whatever your home subnet is, and only traffic heading to that network will be routed through the WireGuard server at your house, but all other traffic goes out of your phone’s normal network paths to the internet.

deleted by creator

WireGuard is free. Obviously my instructions didn’t go into detail about specifically how to set everything up. Port forwarding is required. Knowing your servers external IP address is required. You also need electricity, an ISP subscription, a home server (preferably running Linux), so on and so forth. This is /c/selfhosted after all.

Run WireGuard on some home machine. (Does not need to be the machine the app you want to access is hosted on.)

Run WireGuard on your road warrior system.

There is no step 3.

I’m doing this right now from halfway around the world from my house and it’s been great. Been using iPhone, iPad, and macOS clients connected to linuxserver/WireGuard docker container. Been doing this on many WiFi networks and 5G, no difference.

deleted by creator

deleted by creator

Old enough, as in “my infant is old enough to eat solid foods.”

If your TV OS is old enough there is an API you can use. https://github.com/ow/samsung-frame-art

This was my first thought. I’m actually using this right now to set up WireGuard at my house so I can tunnel there from a remote location on several devices that don’t have ssh accounts on the target.

Next in line is ssh -D 9999 remotehost which opens a socks5 proxy on localhost:9999 that tunnels all connections through the remote host. This is especially rad with proxy.pac https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Proxy_servers_and_tunneling/Proxy_Auto-Configuration_PAC_file

And next in line is ssh -L 9999:target_host:80 (or whatever) which tunnels 127.0.0.1:9999 to target_host:80.