Hacker News Reader

> Major issue I faced in this method

Biggest issue regular user might find with this is that basically all the VPS host' IP ranges are known, and plenty of websites give you a different (worse) experience compared to when using residential addresses, or straight up block you.

Personally I found the hassle to great, compared to using existing VPN services.

Exact same experience here. In the 2010s I ran my own VPN exit node on a dirt cheap VPS so I could access streaming content in my country of birth. Worked great for years, but nowadays so many sites simply block non-residential IP ranges that I gave up ages ago now.

It's a shame because deploying WireGuard was a simple two command process: git checkout followed by a `docker compose up -d` for me etc on a fresh VPS instance.

Yes, but search for "VPS" instead of "Cloud". "Cloud" is a marketing buzzword used to make people pay 10x-500x more than they have to. Although VPS providers are catching on, and starting to label their VPS services as "cloud" now.

Many! OVH has unmetered plans, for example.