Futo (Louis Rossman) at it again with great content, this time a Guide to a Self Managed life. This 14hrs long guide comes in two video parts, aswell as a written guide for those who prefer. Both video and written quide comes with complete chapters and timestamps. This should be a great starting point for those who have the time and want to start learning from the very beginning.
Video Link to Part 1: Youtube - Invidious
Video Link to Part 2: Youtube - Invidious
Happy selfhosting in 2025 everyone ✨
Hey everyone in the comments complaining, this video is for me and other like me not for you. He took time to go through each step as if a complete beginner (aka me) was doing this. That means working through something as simple as downloading pfsense iso. Show me another complete guide that troubleshoots along with me and doesn’t assume everything works perfectly.
He clearly states at the beginning this is not the only way to do this. He also clearly states where things could be better (pf vs OPN) but why momentum has kept him from making a change.
I’m glad y’all are at where y’all are at but this video will help win so many more people over. Having a single tutorial that takes me from zero to a selfhost solution that replicates 80% of google’s everyday offering is HUGE. Is it perfect, probably not? Does it work, looks like it! And hopefully, finally getting something working will give me the confidence to implement improvements or try my own thing.
@Sips thanks for providing this as I might have missed it since it’s not Rossman’s channel. I was disappointed to come into the comments and see more complaints than appreciation. I’ve been thinking about this for a while and occasionally looking at tutorials and guides but everytime it felt like I had to piece meal all the parts to get the features I wanted. This meant troubleshooting each individual tutorial and then hoping it was completely interoperable with the next tutorial for the features/software I want. That kept me from even starting at all. Glad this exists now and knowing Rossman/Futo, it will only be improved as time goes on. Rant over.
@Sunny@slrpnk.net There is absolutely no way any starter will see that page and not be intimidated. I am a well seasoned selfhoster and even I saw that and went “Wow that’s a lotta words and images on a single page.”
Even arch wiki has sensible ToC with pages divided into what the current topic is.
That’s a possibility indeed, but at least he documented all the steps, it’s great to see that because it looks like a lot of work. But I agree at the first that big long page for sure can be intimidated (CTRL+F is your best friend here).
It’s so easy to self host! Just watch 14 hours of a talking head!
Fan of FUTO, but can’t recommend this to most people thinking of starting. Needs to be less “scary”.
Agree! It can only act as a reference. I like the approach taken by distributions like Yunohost where all the details are abstracted away.
I get how momentum keeps you on a path, and he admits that he’d rather use OPNsense in the wiki, but dammit, now he’s got a bunch of other people going down the same pfSense road to the rugpull. And man, Wireguard is so much less confusing and difficult than OpenVPN, but because of the drama the pfSense weirdos made with Donnenfeld over the kernel patches for WG, there’s precious little support for WG in the pfSense environment. Wireguard is definitely more noob friendly.
And if you’re watching this because you need this level of help to selfhost, you definitely should not be hosting email yourself. Love Mailcow, used it for years, but I’m a veteran of the spam wars from way back and know how to deal with the current landscape. He is too, so he should know better.
Rule one of self hosting. Do not self host your own email. Only pain will you find.
You of course can, but there are so many additional hoops you have to jump through. I use my main domain for my email, but proton is one of the few subscriptions I happily pay for
I selfhost my own mail server (my primary mail in fact).
My LE certs expired on Christmas eve, when I was also getting sick. I didn’t realize my mail server was down for a week until about NYE. Luckily Postfix queued all my emails and there was nothing important lost, but I am reevaluating self hosting my mail server. That being said, this was also the worst issue I’ve faced in over a year of self hosting mail. And it only arose because my dumbass still hasn’t automated my certificate rotation.
If you’re using let’s encrypt, it’s worth automating the cert renewals. Even for systems where the automation is difficult and not supported.
It’s also worth running some kind of monitoring system. You can check certificates with OpenSSL really easily. Fire off a message to NTFY.
I’ve been self-hosting email for so long (and ran/consulted on corporate email systems for a long time), I’m pretty sure my original domain (25 years) lends it’s respectability to new domains I host at the same address. The hell of it is I host on a resi IP address and have never had a single blacklist event. I don’t even know how that’s possible other than the fact that I’ve done it for so long with no incidents that I think I’m on a whitelist or something.
@ikidd @scrubbles I’m in a similar situation, though not hosted at home (rather, at a linode VPS with an IP that I don’t think has changed in almost 20 years).
They were set up in 2006, and I’ve only ever had a blacklist event or two related to not adopting/upgrading to some new standard like SPF, rather than any kind of spam thing.
This mentality is backwards. Hosting email has pitfalls yes but in a world where more people do it the less deep those pitfalls will become.
If you are curious and want to host email go for it!
This guide is heavily opinionated and simply outdated. 2 examples:
- use of openvpn. Wireguard is by design way more secure (use of keys instead of passwords) and is way more performant.
- use of pfSense. Yes pfSense is ok but the company behind it has shown it hostility towards open source and foss multiple times. Why should a beginner use PFsense when OPNsense exists. OPNsense is not even mentioned.
And that are only 2 points i discovered while scrolling through. Louis is a great guy but as it looks like he should leave that topic to other people.
I completely agree that WireGuard and OPNsense are excellent choices, and I would have chosen them myself. However, I don’t think it’s fair to suggest that someone should “leave the topic to others” simply because they’ve made different choices. While WireGuard is indeed superior, OpenVPN is still a solid option and widely used today. Similarly, although OPNsense is better, pfSense remains a great piece of software - even though the company behind it isnt perfect.
People should still be able to use whatever software they like without being juged by it. Its better for people to at least start with something, rather than nothing: then its also more likely they will get more educated on topic and the different matters of opinions later on.
OpenVPN is still a solid option and widely used today.
Absolutely, but Wireguard is simpler to setup and comes by default and by design with a more secure default config.
- Create keys on host and on clients
- Generate a config
- You now have a secure VPN Setup.
Now look at all those options you need to tune on OpenVPN.
even though the company behind it isnt perfect.
But then why recommending pfSense? OPNsense is the same with a much more FOSS friendly company behind it. Yes pfSense is at the moment ok but no reason to use it over OPNsense imho.
People should still be able to use whatever software they like without being juged by it.
Yes. And i never judged anyone running thr software, only ppl who recommend it.
Its better for people to at least start with something, rather than nothing
I am not sure about it. Personally, when i get into a new topic i like to have comparisons. They show me what is actually relevant and what i should look out for. But maybe it is just me.
I said multiple times “recommend” here, but that is actually my main problem, i would be much more ok when he simply said there is x and y also available but i use z because of 123…
Also, you must have not read the wiki properly, because he does mention OPNsense.
This is correct, i missed that part. pfSense is mentioned 259 vs. OPNsense 3 times. But only the “not nice part” is mentioned and not the hostility towards FOSS. Here are some examples https://github.com/rapi3/pfsense-is-closed-source
I have not vetted every single claim but just alone that fact that they have this closed source model is enough for not using it. OPNsense is to my knowledge fully open source.
heavily opinionated
Is that of itself not an opinion…?
outdated
Tbf I haven’t looked at the source material but I don’t think two points make it “outdated”. It’s like calling Debian outdated.
Is that of itself not an opinion…?
Nope. It is objectively opinionated, since he only shows his solution and offers or shows no other solution.
Tbf I haven’t looked at the source material but I don’t think two points make it “outdated”. It’s like calling Debian outdated.
Debian is not outdated, also is the technology not outdated he used in the guide (as far as i can tell since i have not read through everything). But using those to get to the shown solution is outdated. When someone in this community asks for a VPN solution most ppl will recommend Wireguard and or tailscale and not OpenVPN.
OpenVPN has other benefits like better user management and more customizability but for this use case it is not the fit, since other solutions are easier to setup and harder to fuck up the security part for a beginner.
Edit: Those are only the 2 examples i picked. I have not looked through everything, but those 2 stood out to me by just looking at the ToC.
Appreciate the written version, though the wiki formatting looks a little weird on mobile. The text on the table of contents is rather small.
