1

I have a small personal website hosted through go-daddy. I also have an old machine sitting in my garage collecting dust. I know enough to make my old dumpy machine a Linux server for my tiny website and save a few bucks on hosting. But what are the biggest risks attached to hosting my own site? What should I know/do before I decide that's the direction I want to go?

closed as too broad by Eric G, Bob Brown, tylerl, Stephane, M'vy Mar 4 '15 at 8:48

Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • 1
    You're not intended on using Windows XP as your web hosting platform, are you? – Xander Mar 3 '15 at 23:36
  • Step 1: assume your server will be taken over in the first week. Step 2: now design your security. – schroeder Mar 3 '15 at 23:56
  • I intend to make it a linux machine. – ShemSeger Mar 4 '15 at 0:04
  • Not related to security, but are you sure that the amount of electricity the server uses won't cost more than the paid hosting? Running a computer 24/7 can cost more in electricity than you'd think. GoDaddy can host sites cheaply because they put tons of sites on a single server with shared hosting. – tlng05 Mar 4 '15 at 0:47
  • @user54791 - A very valid point. It would be interesting to know how much electricity a desktop pc uses in a year... – ShemSeger Mar 4 '15 at 2:58
1

Well if you are hosting from inside your own network then you have a little bit more work to do. ( ps don't use windows , install Linux instead , not only will it be safer but in general all the typical things that you expect to use for hosting a website are designed for Linux , apart from iis windows support is always "hacked in" )

If hosting from a third party provider and assuming that you have no sensitive information stored then you are pretty much set. Just don't reuse passwords and there is nothing of value to worry about.

If hosting from your home network then you effectively have a internet visible IP address which is easy to find ( via your domain name ), so you have to worry about ensuring that everything on that server is completely locked down ( due to the fact that if the web server gets compromised then you have to deal with the possibility that you have a malicious machine on the inside of your home network which gives access to all your data, and the potential to even sniff or inject all network data if your network is appropriately mis configured.

Not the answer you're looking for? Browse other questions tagged or ask your own question.