Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
I don't host my website on my home PC, so I'd weigh in more on the cons side:
- My IP changes every 24 hours or even more often.
- I don't want to go through DynDNS.
- I don't want to publish my home IP because that allows pretty precise geo location.
- Until this year, I was on 12 MBit for download, and I guess 2 MBit for upload. Now I am at 50 MBit down and 10 up, but that's still not too nice for a server.
- I strongly prefer offshore hosting in a country that takes freedom of speech more serious than my own one, though my site is totally harmless and inoffensive (just an open source tech project).
- I don't want to open any incoming ports on my router.
- I'm paying roughly 40 Euro per year for shared hosting (domain not included), that's too little to make a fuss about.
- I think I'm not an experienced enough sys admin to do that properly and leave that to my hosting provider. Sometimes it's more professional to know one's limitations.
- I don't want to take care of the updates and CVEs of the server side, which naturally have a much greater attack area than my client home setup.
- I don't need any advanced features besides basic htaccess and static website serving.
- I don't do backend dev, so I don't need that kind of full control.
- I don't care if there is a total system crash at my hosting provider including complete loss of data because I have a full backup of my website both at home and on my work PC.
Linux446455yI host some stuff.
Unless you are totally broke, it's not worthed...
Condor329465yHosting from home, don't do it. Too many security concerns to take care of. Once the webserver in your home is hacked, the whole home network is out there for grabs. That's why I don't have a single listener accessible to the internet in my home, even though the resource savings and my semi-static IP (it never really changes) tell me otherwise - the resources for it are there, and it'd allow me to do some nice stuff with it. So I am considering to ask my ISP whether I can get a second IP and make my server at home be a passthrough connection (so that it isn't NAT'ed and instead leases an IP directly from the ISP). But such a setup would be on a separate adapter and network, and be heavily monitored because I don't want my home network to get compromised.
Unless you really know what you're doing, get a VPS. On Aruba Cloud (which I use) they start at €1.21 a piece. No support whatsoever so you'll be on your own, and be expected to know your Linux 101. But at least it's outside of your home.
Condor329465y@Linux That's what I'm considering here as well. I've never been able to wrap my head around the idea of DMZ, but that's the isolated network, right? That can communicate with the main (internal) network through routing, but with limited features (set in the firewall). (Edit: rather, the internal network would communicate with the perimeter network, to avoid having internal services accessible to the DMZ.) My main concern is with the ISP though. I've got one public IP, but I'm not sure if they'll be happy if I request a second one from their servers without having their approval to do so first. I mean, nowhere in my plan it's mentioned :/
shahlin4925yThanks guys, just wanted some info on this because I think it's pretty easy to set up a web host. But I guess there are many security concerns and stuff like that so it's not really worth hosting myself.
Not at home but I tent multiple servers so yes, a couple myself.