home server alternatives
Zak Smith
zak at computer.org
Wed Apr 15 03:02:38 UTC 2026
I just have the "home" machine VPN into the remote (colo/VPS) and then
use xinet.d to redirect appropriate ports on the remote to the home.
Works great.
On Tue, Apr 14, 2026 at 08:56:11PM -0600, Daniel Vinci wrote:
> You don't need to with this setup. There are two machines involved, a frontend, and a backend. The frontend is the only thing that needs a "clear" internet connection. This can be a cheap VPS. You then connect to that VPS from the "backend" box that just needs *some* internet connection - even just over WiFi or whatever. The frontend forwards packets to the backend.
>
> On Tue, Apr 14, 2026, at 8:51 PM, Steve Wolf wrote:
> > Assume I'm not going to have any access to the internet hardware, which is why I need some other location to host whatever I migrate my server to. I'm starting to investigate a virtual private server (VPS) at https://www.bluehost.com/ for example.
> >
--
Zak Smith
Please do not send private or confidential information via email.
More information about the NCLUG
mailing list