This post will be showing a simple way to create your own WordPress website. I will go over everything from getting a custom url, getting a remote server, and setting up WordPress. Unfortunately its not free to do this, but it is fairly inexpensive.

Setting up a server

First thing we want to do is set up a server. You can always host your site on your local computer or even your smart phone for free (except for internet costs) but I find it way easier to manage and maintain it from a service. There are many cloud computer services out there such as AWS, Azure, etc. but I will be using Digital Ocean because I find it to be cheap and easy. After creating an account and adding billing info and everything, we can create what they call a droplet, which is just a computer somewhere else in the world.

Pick the size, I went with the cheapest because I don't expect millions of people visiting my site.

Pick the location for the server. For this I picked San Francisco since it's closest for me but ideally you would want to pick the one closest to your target audience since the closer the server is physically to the person, the faster the site loads.

Now the tricky step is using an ssh key. This is a secret key that only you have access to so now one else can get into the server. Github has some nice tutorials on it

After creating an ssh key pair, we can add the public key into the menu, then click create.

It takes a bit of time to set up. Once it's finished, we need to grab our ip address for the next step. That can easily be found by clicking on the droplet name and finding the ip address field.

Aquiring a url

I'm not too familiar with the way it all works, but to my understanding, url domain names are managed by the ICANN organization and you're able to rent them out from registrars or sellers. The registrar I am familiar with and will be using is but there are many others to choose from. All you have to do is go on their site, then search and buy the name you want. They're usually pretty cheap like $10/year but some can get crazy expensive. I bought to put my personal blog on.

After buying out domain name, we go to My Account > My Domains > DNS Record. The DNS is the service that maps the domain name to its ip address. Now, we enter in "www" in the host field and grab the ip address from the previous step and enter it in the "Answer" field, and click "Add Record". This just says that when someone goes to, they get sent to the digital ocean server. We can easily test it by going to that url.

Looks good! We can verify everything is set up by going to the url:

Setting up wordpress

Next is to ssh into the server and wordpress should be enabled. For ssh I like to set up a config to make it easier.

In `~/.ssh/config`, add the lines
Host tylerhaun
User root
IdentityFile ~/.ssh/id_rsa

which makes it so all we have to do is run `ssh tylerhaun` in order to get in. Then as soon as we get it it displays a message saying wordpres has been enabled. All we have to do now is go to our site's url and follow the setup instructions to create an account. After that, it should be functional!

Nothing too special just yet but it gets way easier from here. To make updates, all you have to do is go to $URL/wp-admin and log in (ex.

Securing server

One very important thing is security. There are a couple things we should do to make the server more secure so no hackers get in. One measure is adding ufw. Ufw is the universal firewall and can be set up to block all unwanted traffic Since this is a basic http web server, the only ports that should really be open are 22 for ssh and 80 for http. Everything else should be blocked. It seems the new droplets com preinstalled with it but for reference, we would run

sudo ufw enable
sudo ufw allow 22
sudo ufw allow 80

My old server didn't have this preinstalled, so thats good its on the new ones. The next security enhancement is to create a user. I always here its extremely insecure to have root user be accessible which is why I like to create a regular user. We can enable sudo on the user if we do need to run commands as root, so nothing is really lost from it.

Digital Ocean has a pretty goo guide on thisput link here

The to disable ssh-ing into root, move ssh authorized keys to the created user.

su - username
mkdir .ssh
sudo mv /root/.ssh/authorized_keys .ssh/
sudo chown username:username .ssh/authorized_keys

and on the host computer, update the `~/.ssh/config` User field to username.

One last thing to consider (it also seems fixed) is to disable password ssh authentication, so that only someone with the ssh key can get in. In the file `/etc/ssh/sshd_config`, we can just add / edit the line to be

PasswordAuthentication no


sudo sshd restart

should reload the config.

And those are the big security improvements I can think of to help prevent hackers from taking control.

Now, we have out WordPress server running on the internet and we can customize WordPress and add all the content we want to out hearts desire.