You'll find much better pricing at RackNerd, DediRock, InterServer, BuyVM, etc. Small indy hosting companies are the way to go. 2GB for $5/month or so is the typical price point.
Any host that offers KVM and allows you to upload your own ISO can run OpenBSD (or FreeBSD, NetBSD, whatever you want).
Check out LowEndTalk or LowEndBox for deals. There are other sites but that's where I shop.
Sure, if you need an API, or if you want to host in one of the less common locations, or if you absolutely must have five nines, then DO or Vultr or Linode or Amazon LightSail can be a good fit. But if you just need a VPS with a control panel in a typical hosting location (Amsterdam, LA, New York, Chicago, Singapore, etc.) then I don't see the point of paying more at one of the big hosts.
> Small indy hosting companies ... $5/month or so is the typical price point.
> I don't see the point of paying more at one of the big hosts.
I'm confused. People who are paying $4/mo at the big host should instead save money by paying $5/mo at a small host?
Check out BuyVM 3.50$ plan.
Meanwhile I recently migrated a $5 DigitalOcean VM that's been running flawlessly for over 6 years. It was in dire need of an Ubuntu upgrade. I expect this one to keep going for just as long!
For app hosting I'd either 1) use cloudflared and a cheap Lenovo Tiny box to host from my house, 2) write something serverless that runs on Cloudflare Workers, or 3) use a real host that isn't 18 months old and run by hucksters in a race to the bottom.
The wireguard tunnels haven’t gone down after years of no maintenance use.
However, this part: "Since this is going to be a bare-bones web server we can remove most of the sets.". This is not great advice. Reducing the number of sets even on a headless server can lead to issues with ports depending on libraries Xenocara provides that would then be missing (fonts, etc.). Likewise, when you upgrade the default is to install all sets unless you manually intervene, which could lead to a surprise bump in disk usage that you may not have accounted for. In general, reducing the number of sets should be considered "I am deviating from the defaults and I know what I am doing" territory and Theo keeps threatening to remove the option to select the sets in the installer when people complain and I am inclined to agree with him. So, if you have 10GB of disk in that Droplet, just do the OpenBSD thing and go with the defaults and you will be all the happier for it down the line. Messing with the installation size really is for those rare cases (fitting many VMs on a single host, ancient machines, etc.) where you have no other choice.
joshua stein's interest in getting OpenBSD running on anything he can provides useful insight too https://jcs.org/tagged/openbsd
If you want a book, Absolute OpenBSD is good though a bit out of date now. A lot of it would still be applicable though, if backed up by the current man pages.
Reading undeadly.org is a another good way to keep up on developments.
Thanks for pointing this out and I appreciate the other recommendations in this thread. Massive +1 for @jcs. That dude is awesome and puts out great stuff.
But they are not that small anymore. They are now VC-funded, operate in 36 datacenters worldwide and are currently spending $1 billion to build an AI datacenter in Ohio.
A couple of theories I’ve had is that maybe
a) my VM was compromised and there is a persistent rootkit installed that kills sshd, or
b) file corruption after previous unclean shutdown has left some file needed by sshd corrupted and it leads to this behaviour, or
c) maybe it’s running out of memory sometimes
Each time I want to ssh into the machine I usually have to first connect with the VNC from the vultr dashboard to start sshd up again.
It’s running the latest FreeBSD, as every now and then I log in and do an upgrade on it some time after a new version has been released.
A persistent rootkit may have been installed if it was compromised between when some vulnerability became known and when I later upgraded next time.
If a file was corrupted in an unclean shutdown in the past maybe it’s a file that has not been changed between FreeBSD versions so even though upgrades replace some files maybe it’s the same corrupted file all along.
Ideally I’d just reinstall the machine, but that’s always more of a hassle than it should be so I continue running the VM in this broken state where sshd keeps dying every now and then.
It will only take a few min..
While I’m at it I also took a quick look now at output of `top` and it’s sitting at 27 MB free RAM lol. So from that, out of memory is very likely the reason I keep having sshd die on me.
sshd_oomprotect=YES
Then run service sshd restartPreviously I haven't seen much detailed reason for why it dies in system messages. But this time it said something very specific:
> sshd[2036]: fatal: pack_hostkeys: serialize hostkey private: string is too large
Which kind of sounds like one of the sshd hostkey files might be corrupt? And maybe it only triggers after a while becuase it happens when scanners try to connect to it and during ssh negotiation sshd ends up selecting a different hostkey type than the one it uses when I connect to the machine myself?
I'm going to regenerate all of the three hostkey files on the server, and after that also disable the two that I can do without anyway.
rootbsd.net before that, but they don't seem to exist anymore.
And to clarify, this means encrypt it before it gets to the VPS. Just having full-disk encryption is not enough because cloud providers can dump RAM. There are tools that easily extract encryption keys from RAM.
So, really, you need to trust the cloud provider unless everything is encrypted on computers you own.
Switched to OVH immediately.
Otherwise, I hosted a site with them for years and all went well.
P/S: The website is running on a Raspberry Pi 3 in my house, hope HN won't hug it to dead
I ended up turning that off and switching to Tailscale. Tailscale is set to advertise my home IP range (I chose one that's not 192.168 based which avoids problems with range conflicts). So I can just connect to Tailscale and connect to 10.X.Y.Z as though I'm home. If I want memorable hostnames I can point DNS records to those private IPs.
https://news.ycombinator.com/item?id=49207236
e.g. Hetzner tripled prices recently.
The fact that they donate back to OpenBSD is great though. I own a VM there for testing stuff.
It is a small and no frills service but the sys-admin, who runs the project, is very helpful and attentive. That is to say probably much better and human customer service than the big players. There are definite downsides, but if a project fits, highly recommended.
Look on webhostingtalk or lowendbox or lowendtalk.
None of the dedicated machines I found were cheaper, so I'm surprised someone is offering that for $35/month.
This is kind of exactly what I worry about with a dedicated box. That and hardware failure.